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

Posted by

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

Unauthenticated PHP Item Injection

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

The purpose of the plugin is to stop spam in remarks, kinds, and sign-up registrations. It can stop spam bots and has the capability for users to input IP addresses to obstruct.

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

Unexpected inputs should be filtered out. That filtering process that stays out undesirable inputs is called sanitization.

For instance, a contact kind need to have a function that inspects what is sent and block (sanitize) anything that is not text.

The vulnerability found in the anti-spam plugin enabled encoded input (base64 encoded) which can then activate a kind of vulnerability called a PHP Object injection vulnerability.

The description of the vulnerability released on the WPScan site describes the concern as:

“The plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are utilized as second difficulty, which might lead to PHP Object injection if a plugin set up on the blog has an appropriate gizmo chain …”

The classification of the vulnerability is Insecure Deserialization.

The non-profit Open Web Application Security Task (OWASP) describes the possible effect of these kinds of vulnerabilities as severe, which may or might not hold true specific to this vulnerability.

The description at OWASP:

“The effect of deserialization defects can not be overstated. These flaws can result in remote code execution attacks, one of the most severe attacks possible.The organization impact depends on the defense needs of the application and information. “However OWASP likewise keeps in mind that exploiting this sort of vulnerability tends to be difficult:”Exploitation of deserialization is somewhat tough,

as off the shelf exploits hardly ever work without changes or tweaks to the hidden exploit code.”The vulnerability in the Stop Spammers Security WordPress

plugin was fixed in variation 2022.6 The main Stop Spammers Security changelog (a description with dates of different updates)keeps in mind the fix as an improvement for security. Users of the Stop Spam Security plugin must think about upgrading to the most recent

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

: CVE-2022-4120 Information Check out the WPScan publication of details associated with this vulnerability:

Stop Spammers Security