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

Posted by

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

Unauthenticated PHP Item Injection

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

The function of the plugin is to stop spam in comments, forms, and sign-up registrations. It can stop spam bots and has the ability for users to input IP addresses to block.

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

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

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

The vulnerability found in the anti-spam plugin enabled encoded input (base64 encoded) which can then trigger a type of vulnerability called a PHP Item 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 second obstacle, which might result in PHP Things injection if a plugin set up on the blog has an appropriate gadget chain …”

The classification of the vulnerability is Insecure Deserialization.

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

The description at OWASP:

“The effect of deserialization defects can not be overemphasized. These flaws can lead to remote code execution attacks, one of the most severe attacks possible.The service effect depends on the security needs 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 somewhat challenging,

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

plugin was fixed in variation 2022.6 The main Stop Spammers Security changelog (a description with dates of different updates)notes the fix as an enhancement for security. Users of the Stop Spam Security plugin should think about updating to the current

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

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

Stop Spammers Security