WordPress Anti-Spam Plugin Vulnerability Impacts As Much As 60,000+ Sites

Posted by

A WordPress anti-spam plugin with over 60,000 setups covered a PHP Object injection vulnerability that emerged from improper sanitization of inputs, subsequently permitting base64 encoded user input.

Unauthenticated PHP Item Injection

A vulnerability was found in the popular Stop Spammers Security|Block Spam Users, Comments, Kinds WordPress plugin.

The function of the plugin is to stop spam in comments, forms, and sign-up registrations. It can stop spam bots and has the capability for users to input IP addresses to block.

It is a required practice for any WordPress plugin or type that accepts a user input to just enable particular inputs, like text, images, email addresses, whatever input is anticipated.

Unforeseen inputs must be removed. That filtering process that stays out undesirable inputs is called sanitization.

For instance, a contact type ought to have a function that inspects what is sent and block (sterilize) anything that is not text.

The vulnerability discovered in the anti-spam plugin allowed encoded input (base64 encoded) which can then set off a kind of vulnerability called a PHP Things injection vulnerability.

The description of the vulnerability released on the WPScan site explains the problem as:

“The plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are used as second challenge, which could lead to PHP Object injection if a plugin installed on the blog has an ideal gadget chain …”

The category of the vulnerability is Insecure Deserialization.

The non-profit Open Web Application Security Project (OWASP) explains the possible effect of these sort of vulnerabilities as severe, which may or might not be the case specific to this vulnerability.

The description at OWASP:

“The impact of deserialization defects can not be overstated. These defects can lead to remote code execution attacks, among the most severe attacks possible.The service impact depends on the security needs of the application and data. “But OWASP likewise keeps in mind that exploiting this sort of vulnerability tends to be tough:”Exploitation of deserialization is somewhat tough,

as off the shelf exploits rarely work without modifications or tweaks to the underlying make use of code.”The vulnerability in the Stop Spammers Security WordPress

plugin was repaired in variation 2022.6 The official Stop Spammers Security changelog (a description with dates of various updates)notes the fix as an enhancement for security. Users of the Stop Spam Security plugin ought to consider updating to the current

version in order to avoid a hacker from exploiting the plugin. Read the official notification at the United States Government National Vulnerability Database

: CVE-2022-4120 Detail Check out the WPScan publication of information connected to this vulnerability:

Stop Spammers Security