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

Posted by

A WordPress anti-spam plugin with over 60,000 installations covered a PHP Object injection vulnerability that developed from incorrect sanitization of inputs, consequently permitting base64 encoded user input.

Unauthenticated PHP Object Injection

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

The purpose 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 required practice for any WordPress plugin or type that accepts a user input to only allow specific inputs, like text, images, e-mail addresses, whatever input is anticipated.

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

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

The vulnerability found in the anti-spam plugin enabled encoded input (base64 encoded) which can then activate a type of vulnerability called a PHP Item 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 utilized as second difficulty, which could cause PHP Object injection if a plugin set up on the blog has a suitable gadget chain …”

The classification of the vulnerability is Insecure Deserialization.

The non-profit Open Web Application Security Job (OWASP) describes the potential effect of these sort of vulnerabilities as major, which may or might not be the case particular to this vulnerability.

The description at OWASP:

“The impact of deserialization flaws can not be overemphasized. These flaws can cause remote code execution attacks, among the most serious attacks possible.The service impact depends upon the defense requirements of the application and information. “But OWASP likewise keeps in mind that exploiting this kind of vulnerability tends to be tough:”Exploitation of deserialization is rather challenging,

as off the shelf makes use of rarely work without modifications or tweaks to the underlying 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 enhancement for security. Users of the Stop Spam Security plugin ought to think about upgrading to the most recent

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

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

Stop Spammers Security