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

Posted by

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

Unauthenticated PHP Item Injection

A vulnerability was found in the popular Stop Spammers Security|Block Spam Users, Remarks, Kinds 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 capability 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 specific inputs, like text, images, e-mail addresses, whatever input is anticipated.

Unanticipated inputs need to be strained. That filtering process that stays out unwanted inputs is called sanitization.

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

The vulnerability found in the anti-spam plugin allowed encoded input (base64 encoded) which can then set off a type of vulnerability called a PHP Item 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 used as second obstacle, which could lead to PHP Things injection if a plugin installed on the blog site has a suitable gadget chain …”

The category of the vulnerability is Insecure Deserialization.

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

The description at OWASP:

“The impact of deserialization defects can not be overstated. These defects can cause remote code execution attacks, one of the most serious attacks possible.The service effect depends upon the defense needs of the application and information. “But OWASP also notes that exploiting this kind of vulnerability tends to be tough:”Exploitation of deserialization is somewhat challenging,

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

plugin was fixed in version 2022.6 The official 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 should consider updating to the latest

version in order to avoid a hacker from making use of the plugin. Check out the main notification at the United States Federal Government National Vulnerability Database

: CVE-2022-4120 Information Read the WPScan publication of information associated with this vulnerability:

Stop Spammers Security