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

Posted by

A WordPress anti-spam plugin with over 60,000 setups covered a PHP Item injection vulnerability that emerged from incorrect sanitization of inputs, consequently permitting 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 block.

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

Unexpected inputs must be filtered out. That filtering procedure that keeps out undesirable inputs is called sanitization.

For example, a contact form should have a function that examines what is submitted and block (sterilize) anything that is not text.

The vulnerability discovered in the anti-spam plugin permitted encoded input (base64 encoded) which can then set off a kind of vulnerability called a PHP Things injection vulnerability.

The description of the vulnerability released on the WPScan website explains the problem as:

“The plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are utilized as 2nd difficulty, which might lead to PHP Object injection if a plugin set up on the blog site has a suitable gadget chain …”

The classification of the vulnerability is Insecure Deserialization.

The non-profit Open Web Application Security Task (OWASP) describes the possible effect of these sort of vulnerabilities as serious, which might or might not hold true specific to this vulnerability.

The description at OWASP:

“The effect of deserialization flaws can not be overstated. These flaws can lead to remote code execution attacks, among the most severe attacks possible.The service impact depends on the protection needs of the application and information. “However OWASP also keeps in mind that exploiting this type of vulnerability tends to be tough:”Exploitation of deserialization is rather difficult,

as off the rack makes use of hardly ever work without modifications or tweaks to the underlying make use of 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 various updates)keeps in mind the repair as an improvement for security. Users of the Stop Spam Security plugin need to think about updating to the latest

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

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

Stop Spammers Security