WordPress Anti-Spam Plugin Vulnerability Impacts As Much As 60,000+ Sites

Posted by

A WordPress anti-spam plugin with over 60,000 installations covered a PHP Things injection vulnerability that occurred from incorrect 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, Kinds WordPress plugin.

The function of the plugin is to stop spam in comments, kinds, 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 type that accepts a user input to just enable particular inputs, like text, images, email addresses, whatever input is anticipated.

Unanticipated inputs need to be removed. That filtering process that keeps out undesirable inputs is called sanitization.

For instance, a contact form must have a function that inspects what is submitted and block (sanitize) anything that is not text.

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

The category of the vulnerability is Insecure Deserialization.

The non-profit Open Web Application Security Job (OWASP) describes the possible impact of these kinds of vulnerabilities as severe, which might or might not hold true particular 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 service impact depends upon the security needs of the application and data. “But OWASP likewise notes that exploiting this type of vulnerability tends to be difficult:”Exploitation of deserialization is somewhat challenging,

as off the shelf makes use of seldom work without changes or tweaks to the hidden exploit code.”The vulnerability in the Stop Spammers Security WordPress

plugin was repaired in variation 2022.6 The official Stop Spammers Security changelog (a description with dates of various updates)notes the repair as an enhancement for security. Users of the Stop Spam Security plugin ought to consider upgrading to the latest

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

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

Stop Spammers Security