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 Things injection vulnerability that developed from incorrect sanitization of inputs, consequently enabling base64 encoded user input.

Unauthenticated PHP Things Injection

A vulnerability was found in the popular Stop Spammers Security|Block Spam Users, Comments, Types 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 obstruct.

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.

Unanticipated inputs need to be strained. That filtering process that stays out undesirable inputs is called sanitization.

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

The description of the vulnerability published on the WPScan site describes the issue as:

“The plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are utilized as second challenge, which might lead to 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 Task (OWASP) explains the prospective impact of these sort of vulnerabilities as serious, which might or might not hold true particular to this vulnerability.

The description at OWASP:

“The impact of deserialization flaws can not be overstated. These flaws can cause remote code execution attacks, among the most severe attacks possible.The business impact depends on the protection needs of the application and information. “But OWASP likewise notes that exploiting this sort of vulnerability tends to be hard:”Exploitation of deserialization is rather difficult,

as off the shelf exploits rarely work without changes or tweaks to the underlying exploit code.”The vulnerability in the Stop Spammers Security WordPress

plugin was fixed in variation 2022.6 The official Stop Spammers Security changelog (a description with dates of different updates)notes the fix as an improvement for security. Users of the Stop Spam Security plugin need to consider updating to the most recent

variation in order to avoid a hacker from exploiting the plugin. Check out the official notice at the United States Federal Government National Vulnerability Database

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

Stop Spammers Security