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

Posted by

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

Unauthenticated PHP Object 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, forms, and sign-up registrations. It can stop spam bots and has the ability for users to input IP addresses to obstruct.

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 expected.

Unexpected inputs ought to be strained. That filtering procedure that keeps out unwanted inputs is called sanitization.

For example, a contact form should have a function that inspects what is sent and block (sterilize) anything that is not text.

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

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

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

The category of the vulnerability is Insecure Deserialization.

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

The description at OWASP:

“The effect of deserialization defects can not be overstated. These defects can result in remote code execution attacks, among the most serious attacks possible.The company impact depends upon the security requirements of the application and data. “However OWASP likewise notes that exploiting this kind of vulnerability tends to be difficult:”Exploitation of deserialization is somewhat challenging,

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

plugin was repaired in variation 2022.6 The main 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 need to think about updating to the latest

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

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

Stop Spammers Security