{"id":26038,"date":"2022-12-27T11:12:17","date_gmt":"2022-12-27T11:12:17","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/27\/wordpress-anti-spam-plugin-vulnerability-affects-up-to-60000-sites\/"},"modified":"2022-12-27T11:12:17","modified_gmt":"2022-12-27T11:12:17","slug":"wordpress-anti-spam-plugin-vulnerability-affects-up-to-60000-sites","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/27\/wordpress-anti-spam-plugin-vulnerability-affects-up-to-60000-sites\/","title":{"rendered":"WordPress Anti-Spam Plugin Vulnerability Affects Up To 60,000+ Sites"},"content":{"rendered":"

<\/a>\n
<\/p>\n

\n

A WordPress anti-spam plugin with over 60,000 installations patched a PHP Object injection vulnerability that arose from improper sanitization of inputs, subsequently allowing base64 encoded user input.<\/p>\n

Unauthenticated PHP Object Injection<\/h2>\n

A vulnerability was discovered in the popular Stop Spammers Security | Block Spam Users, Comments, Forms WordPress plugin.<\/p>\n

The purpose of the plugin is to stop spam in comments, forms, and sign-up registrations. It can stop spam bots and has the ability for users to input IP addresses to block.<\/p>\n

It is a required practice for any WordPress plugin or form that accepts a user input to only allow specific inputs, like text, images, email addresses, whatever input is expected.<\/p>\n

Unexpected inputs should be filtered out. That filtering process that keeps out unwanted inputs is called sanitization<\/em>.<\/p>\n

For example, a contact form should have a function that inspects what is submitted and block (sanitize) anything that is not text.<\/p>\n

The vulnerability discovered in the anti-spam plugin allowed encoded input (base64 encoded) which can then trigger a type of vulnerability called a PHP Object injection vulnerability.<\/p>\n

The description of the vulnerability published<\/a> on the WPScan website describes the issue as:<\/p>\n

\n

\u201cThe plugin passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are used as second challenge, which could lead to PHP Object injection if a plugin installed on the blog has a suitable gadget chain\u2026\u201d<\/p>\n<\/blockquote>\n

The classification of the vulnerability is Insecure Deserialization<\/em>.<\/p>\n

The non-profit Open Web Application Security Project (OWASP) describes the potential impact of these kinds of vulnerabilities as serious, which may or may not be the case specific to this vulnerability.<\/p>\n

The description<\/a> at OWASP:<\/p>\n

\n

\u201cThe impact of deserialization flaws cannot be overstated. These flaws can lead to remote code execution attacks, one of the most serious attacks possible.
The business impact depends on the protection needs of the application and data.\u201d<\/p>\n<\/blockquote>\n

But OWASP also notes that exploiting this kind of vulnerability tends to be difficult:<\/p>\n

\n

\u201cExploitation of deserialization is somewhat difficult, as off the shelf exploits rarely work without changes or tweaks to the underlying exploit code.\u201d<\/p>\n<\/blockquote>\n

The vulnerability in the Stop Spammers Security WordPress plugin was fixed in version 2022.6<\/p>\n

The official Stop Spammers Security changelog<\/a> (a description with dates of various updates) notes the fix as an enhancement for security.<\/p>\n

Users of the Stop Spam Security plugin should consider updating to the latest version in order to prevent a hacker from exploiting the plugin.<\/p>\n

Read the official notification at the United States Government National Vulnerability Database:<\/p>\n

CVE-2022-4120 Detail<\/a><\/p>\n

Read the WPScan publication of details related to this vulnerability:<\/p>\n

Stop Spammers Security < 2022.6 \u2013 Unauthenticated PHP Object Injection<\/a><\/p>\n

Featured image by Shutterstock\/Luis Molinero<\/p>\n<\/div>\n