WordPress Anti-Spam Plugin Vulnerability Affects Approximately 60,000+ Sites

Posted by

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

Unauthenticated PHP Object Injection

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

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

It is a required practice for any WordPress plugin or form that accepts a user input to only allow specific inputs, like text, images, e-mail addresses, whatever input is expected.

Unanticipated inputs must be strained. That filtering procedure that stays out unwanted inputs is called sanitization.

For instance, a contact kind should have a function that checks what is submitted and block (sterilize) anything that is not text.

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

The description of the vulnerability published on the WPScan site describes the issue as:

“The plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are utilized as 2nd difficulty, which could lead to PHP Item injection if a plugin installed on the blog site has an appropriate gadget chain …”

The category of the vulnerability is Insecure Deserialization.

The non-profit Open Web Application Security Project (OWASP) describes the prospective impact of these type of vulnerabilities as severe, which might or may not be the case specific to this vulnerability.

The description at OWASP:

“The effect of deserialization defects can not be overstated. These defects can cause remote code execution attacks, one of the most severe attacks possible.The business impact depends upon the protection requirements of the application and data. “However OWASP likewise keeps in mind that exploiting this type of vulnerability tends to be hard:”Exploitation of deserialization is somewhat difficult,

as off the shelf makes use of seldom work without changes or tweaks to the underlying exploit code.”The vulnerability in the Stop Spammers Security WordPress

plugin was repaired in version 2022.6 The main Stop Spammers Security changelog (a description with dates of numerous updates)keeps in mind the repair as an enhancement for security. Users of the Stop Spam Security plugin need to consider updating to the latest

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

: CVE-2022-4120 Detail Read the WPScan publication of details related to this vulnerability:

Stop Spammers Security