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

Posted by

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

Unauthenticated PHP Things Injection

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

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

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

Unanticipated inputs need to be strained. That filtering procedure that keeps out unwanted inputs is called sanitization.

For example, a contact form need to have a function that examines what is sent and block (sanitize) anything that is not text.

The vulnerability discovered in the anti-spam plugin allowed encoded input (base64 encoded) which can then activate a kind of vulnerability called a PHP Object injection vulnerability.

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

“The plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are used as 2nd obstacle, which might lead to PHP Item injection if a plugin installed on the blog has an ideal gizmo chain …”

The classification of the vulnerability is Insecure Deserialization.

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

The description at OWASP:

“The effect of deserialization flaws can not be overemphasized. These defects can result in remote code execution attacks, one of the most major attacks possible.The service effect depends on the protection requirements of the application and data. “But OWASP likewise keeps in mind that exploiting this sort of vulnerability tends to be difficult:”Exploitation of deserialization is somewhat challenging,

as off the rack makes use of seldom work without modifications or tweaks to the underlying make use of 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 various updates)keeps in mind the fix as an improvement for security. Users of the Stop Spam Security plugin ought to consider updating to the most recent

variation in order to prevent a hacker from exploiting the plugin. Read the official alert at the United States Government National Vulnerability Database

: CVE-2022-4120 Information Check out the WPScan publication of information related to this vulnerability:

Stop Spammers Security