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

Posted by

A WordPress anti-spam plugin with over 60,000 installations patched a PHP Item injection vulnerability that occurred from inappropriate sanitization of inputs, subsequently permitting base64 encoded user input.

Unauthenticated PHP Item Injection

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

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

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

Unforeseen inputs ought to be removed. That filtering procedure that keeps out unwanted inputs is called sanitization.

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

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

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

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

The classification of the vulnerability is Insecure Deserialization.

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

The description at OWASP:

“The impact of deserialization flaws can not be overstated. These defects can cause remote code execution attacks, one of the most major attacks possible.The service impact depends upon the security requirements 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 rather challenging,

as off the shelf exploits seldom work without modifications or tweaks to the hidden exploit 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)keeps in mind the repair as an improvement for security. Users of the Stop Spam Security plugin must consider upgrading to the most recent

variation in order to avoid a hacker from exploiting the plugin. Check out the main notification at the United States Government National Vulnerability Database

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

Stop Spammers Security