OOPSpam Anti-Spam <= 1.1.44 - Cross-Site Request Forgery via empty_ham_entries and empty_spam_entries
Strategic Overview
- Status
- Patched in 1.1.45
- Affected Version
< 1.1.45- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-35913
At a glance
CVE-2023-35913 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the OOPSpam Anti-Spam WordPress plugin, affecting versions < 1.1.45. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.45; sites on affected versions should update now. Disclosed June 2023, reported by Skalucy.
Vulnerability Overview
The OOPSpam Anti-Spam plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.44. This is due to missing or incorrect nonce validation on the 'empty_ham_entries' and 'empty_spam_entries' functions. This makes it possible for unauthenticated attackers to delete both spam and legitimate entries via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
OOPSpam Anti-Spam < 1.1.45 carries this weakness at empty_ham_entries, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For OOPSpam Anti-Spam the fix is 1.1.45: builds < 1.1.45 are affected, anything from 1.1.45 onward is not.
Remediation
Update to version 1.1.45, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to OOPSpam Anti-Spam: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: OOPSpam Anti-Spam 1.1.45 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA)
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C