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

Posted by

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

Unauthenticated PHP Things Injection

A vulnerability was discovered in the popular Stop Spammers Security|Block Spam Users, Remarks, Kinds 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 required practice for any WordPress plugin or type that accepts a user input to only permit specific inputs, like text, images, e-mail addresses, whatever input is anticipated.

Unanticipated inputs must be strained. That filtering procedure that keeps out undesirable inputs is called sanitization.

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

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

The description of the vulnerability published on the WPScan site explains the problem as:

“The plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are used as 2nd difficulty, which could lead to PHP Things 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 Job (OWASP) describes the potential impact of these kinds of vulnerabilities as serious, which may or may not hold true specific to this vulnerability.

The description at OWASP:

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

as off the shelf makes use of rarely work without changes 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)notes the repair as an improvement for security. Users of the Stop Spam Security plugin need to consider upgrading to the latest

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

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

Stop Spammers Security