OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) <= 1.2.53 — Unauthenticated IP Header Spoofing
CVE-2025-12094Published · Updated Action summary
Affected: ≤1.2.53Update to 1.2.54 or newer
All remediation steps- Severity
- Medium5.3
- CVSS
- 5.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) oopspam-anti-spam
- Affected≤ 1.2.53
- Patched in1.2.54
Update to 1.2.54 or newer.
You are affected if you run ≤ 1.2.53. Version 1.2.54 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA).
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 1.2.54, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Jonas Benjamin Friedli.
The OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) plugin for WordPress is vulnerable to IP Header Spoofing in all versions up to, and including, 1.2.53. This is due to the plugin trusting client-controlled forwarded headers (such as CF-Connecting-IP, X-Forwarded-For, and others) without verifying that those headers originate from legitimate, trusted proxies. This makes it possible for unauthenticated attackers to spoof their IP address and bypass IP-based security controls, including blocked IP lists and rate limiting protections, by sending arbitrary HTTP headers with their requests.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA)
All 4| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.2 | Unauthenticated Stored Cross-Site Scripting ≤1.2.62Update to 1.2.63 | CVE-2026-32544 | |
| Medium5.4 | Cross-Site Request Forgery via empty_ham_entries and empty_spam_entries <1.1.45Update to 1.1.45 | CVE-2023-35913 | |
| Medium5.5 | Authenticated (Admin+) Stored Cross-Site Scripting ≤1.1.35Update to 1.1.36 | CVE-2023-22716 |
- High7.2Unauthenticated Stored Cross-Site Scripting
≤1.2.62Update to 1.2.63
- Medium5.4Cross-Site Request Forgery via empty_ham_entries and empty_spam_entries
<1.1.45Update to 1.1.45
- Medium5.5Authenticated (Admin+) Stored Cross-Site Scripting
≤1.1.35Update to 1.1.36
Timeline
CVE published
Severity medium, CVSS 5.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.