Unauthenticated IP spoofing via trusted proxy headers
Published Oct 31, 2025 · Updated Oct 31, 2025
IP header spoofing in OOPSpam Anti-Spam 1.2.53 and earlier allows remote attackers to bypass IP-based controls via HTTP headers. The plugin's IP detection logic accepts CF-Connecting-IP, X-Forwarded-For, and other forwarded headers without confirming that a trusted proxy supplied them. No authentication or user interaction is required; a crafted request can evade blocked-IP lists and rate limits, enabling submissions under an attacker-chosen source address.
Summary
What happened
IP header spoofing in OOPSpam Anti-Spam 1.2.53 and earlier allows remote attackers to bypass IP-based controls via HTTP headers. The plugin's IP detection logic accepts CF-Connecting-IP, X-Forwarded-For, and other forwarded headers without confirming that a trusted proxy supplied them. No authentication or user interaction is required; a crafted request can evade blocked-IP lists and rate limits, enabling submissions under an attacker-chosen source address.
The record
- CVE
- CVE-2025-12094
- Published
- Oct 31, 2025
- Updated
- Oct 31, 2025
- Vendor
- OOPSpam
- Product
- OOPSpam Anti-Spam
- Classifications
- CWE-693
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 31, 2025CVE publishedPublication date reported by the CVE source.
- Oct 31, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=1.2.53
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo