oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA)
oopspam-anti-spam · plugin
Known security vulnerabilities for oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA). Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
3 exploitable without logging in · latest Mar 25, 2026
Listed on wordpress.org · latest 1.2.85 · last updated Oct 2, 2026 · 6K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2023-35913unauthenticated · needs a click≤ 1.1.44
WordPress OOPSpam Anti-Spam Plugin <= 1.1.44 is vulnerable to Cross Site Request Forgery (CSRF)
- High 7.1
CVE-2026-32544unauthenticated · needs a click≤ <= 1.2.62
WordPress OOPSpam Anti-Spam plugin <= 1.2.62 - Cross Site Scripting (XSS) vulnerability
- Medium 5.3
CVE-2025-12094unauthenticated≤ 1.2.53
OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) <= 1.2.53 - Unauthenticated IP Header Spoofing
- Medium 4.8
CVE-2023-22716admin≤ 1.1.35
WordPress OOPSpam Anti-Spam Plugin <= 1.1.35 is vulnerable to Cross Site Scripting (XSS)
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).