WordPress Anti-Spam Plugin Vulnerability Impacts 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 occurred from inappropriate sanitization of inputs, consequently 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 comments, kinds, and sign-up registrations. It can stop spam bots and has the ability for users to input IP addresses to obstruct.

It is a needed practice for any WordPress plugin or type that accepts a user input to just enable specific inputs, like text, images, email addresses, whatever input is anticipated.

Unforeseen inputs must be removed. That filtering process that stays out unwanted inputs is called sanitization.

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

The vulnerability found in the anti-spam plugin allowed encoded input (base64 encoded) which can then trigger a kind 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 Item injection if a plugin set up on the blog site has a suitable gadget chain …”

The classification of the vulnerability is Insecure Deserialization.

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

The description at OWASP:

“The effect of deserialization flaws can not be overemphasized. These defects can lead to remote code execution attacks, among the most major attacks possible.The organization impact 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 hard:”Exploitation of deserialization is somewhat difficult,

as off the shelf makes use of seldom work without changes or tweaks to the hidden make use of 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 numerous updates)keeps in mind the fix as an improvement for security. Users of the Stop Spam Security plugin must think about updating to the current

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

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

Stop Spammers Security