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

Posted by

A WordPress anti-spam plugin with over 60,000 installations covered a PHP Object injection vulnerability that emerged from incorrect 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, Forms WordPress plugin.

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

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

Unexpected inputs must be strained. That filtering process that stays out undesirable 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 found in the anti-spam plugin permitted encoded input (base64 encoded) which can then activate a type of vulnerability called a PHP Object injection vulnerability.

The description of the vulnerability released 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 challenge, which might result in PHP Things injection if a plugin installed on the blog has a suitable device 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 major, which might or may not hold true specific to this vulnerability.

The description at OWASP:

“The effect of deserialization defects can not be overstated. These flaws can cause remote code execution attacks, among the most major attacks possible.The organization effect depends on the protection requirements of the application and information. “However OWASP likewise notes that exploiting this type of vulnerability tends to be challenging:”Exploitation of deserialization is somewhat difficult,

as off the rack exploits seldom work without modifications or tweaks to the hidden make use of code.”The vulnerability in the Stop Spammers Security WordPress

plugin was fixed in version 2022.6 The main Stop Spammers Security changelog (a description with dates of different updates)notes the repair as an enhancement for security. Users of the Stop Spam Security plugin must consider upgrading to the current

version in order to prevent a hacker from making use of the plugin. Check out the main alert 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