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

Posted by

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

Unauthenticated PHP Things Injection

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

The function 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 block.

It is a required practice for any WordPress plugin or type that accepts a user input to just allow specific inputs, like text, images, email addresses, whatever input is anticipated.

Unanticipated inputs ought to be filtered out. That filtering process that keeps out unwanted inputs is called sanitization.

For instance, a contact kind 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 allowed encoded input (base64 encoded) which can then trigger a type of vulnerability called a PHP Object injection vulnerability.

The description of the vulnerability published on the WPScan website explains the concern as:

“The plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are used as 2nd difficulty, which might cause PHP Item injection if a plugin set up on the blog has an appropriate device chain …”

The classification of the vulnerability is Insecure Deserialization.

The non-profit Open Web Application Security Project (OWASP) describes the possible impact of these kinds of vulnerabilities as severe, which may or might not be the case specific to this vulnerability.

The description at OWASP:

“The effect of deserialization flaws can not be overstated. These defects can cause remote code execution attacks, among the most serious attacks possible.The company effect depends on the security needs of the application and information. “But OWASP likewise notes that exploiting this type of vulnerability tends to be challenging:”Exploitation of deserialization is rather hard,

as off the shelf exploits hardly ever work without modifications or tweaks to the hidden 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 repair as an improvement for security. Users of the Stop Spam Security plugin need to consider updating to the most recent

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

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

Stop Spammers Security