Peter’s Custom Anti-Spam <= 3.2.3 - Cross-Site Request Forgery via cas_register_post Function
Strategic Overview
- Status
- Patched in 3.2.4
- Affected Plugin
- Peter’s Custom Anti-Spam
- Affected Version
<= 3.2.3- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-12554
At a glance
CVE-2024-12554 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Peter’s Custom Anti-Spam WordPress plugin, affecting versions <= 3.2.3. 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 3.2.4; sites on affected versions should update now. Disclosed December 2024, reported by SOPROBRO.
Vulnerability Overview
The Peter’s Custom Anti-Spam plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.2.3. This is due to missing nonce validation on the cas_register_post() function. This makes it possible for unauthenticated attackers to blacklist emails 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)
Peter’s Custom Anti-Spam <= 3.2.3 carries this weakness at cas_register_post(), 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 Peter’s Custom Anti-Spam the fix is 3.2.4: builds <= 3.2.3 are affected, anything from 3.2.4 onward is not.
Remediation
Update to version 3.2.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Peter’s Custom Anti-Spam: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Peter’s Custom Anti-Spam 3.2.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Peter’s Custom Anti-Spam
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C