Peter’s Custom Anti-Spam
peters-custom-anti-spam-image · plugin
Known security vulnerabilities for Peter’s Custom Anti-Spam. Find out in seconds which version runs on your site with WP Lens.
2 known vulnerabilities
2 exploitable without logging in · latest Dec 18, 2024
Before you install
Use with care
- 1 record needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 3.2.4 · last updated Dec 17, 2024 · 200+ installs
wordpress.org status checked on Nov 7, 2026
Vulnerabilities
- Medium 6.1
CVE-2023-45759unauthenticated · needs a click≤ 3.2.2
WordPress Peter’s Custom Anti-Spam Plugin <= 3.2.2 is vulnerable to Cross Site Scripting (XSS)
- Medium 5.4
CVE-2024-12554unauthenticated · needs a click≤ 3.2.3
Peter’s Custom Anti-Spam <= 3.2.3 - Cross-Site Request Forgery via cas_register_post Function
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).