WordPress Anti-Spam Plugin Vulnerability Impacts Up To 60,000+ Websites

Posted by

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

Unauthenticated PHP Things Injection

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

The purpose of the plugin is to stop spam in comments, types, 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 permit particular inputs, like text, images, email addresses, whatever input is anticipated.

Unforeseen inputs ought to be filtered out. That filtering process that stays out undesirable inputs is called sanitization.

For example, a contact type should have a function that examines what is sent and block (sanitize) anything that is not text.

The vulnerability found in the anti-spam plugin allowed encoded input (base64 encoded) which can then trigger a kind of vulnerability called a PHP Things 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 obstacle, which might lead to PHP Object injection if a plugin installed on the blog has a suitable gizmo chain …”

The category of the vulnerability is Insecure Deserialization.

The non-profit Open Web Application Security Project (OWASP) explains the prospective impact of these kinds of vulnerabilities as severe, which might or might not hold true specific to this vulnerability.

The description at OWASP:

“The impact of deserialization defects can not be overemphasized. These flaws can cause remote code execution attacks, among the most serious attacks possible.The business effect depends upon the protection needs of the application and information. “However OWASP also keeps in mind that exploiting this kind of vulnerability tends to be challenging:”Exploitation of deserialization is rather hard,

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

plugin was repaired in version 2022.6 The official Stop Spammers Security changelog (a description with dates of different updates)keeps in mind the fix as an improvement for security. Users of the Stop Spam Security plugin need to consider updating to the most recent

variation in order to prevent a hacker from making use of the plugin. Check out the main notice at the United States Federal Government National Vulnerability Database

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

Stop Spammers Security