CVE-2025-12094

OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) <= 1.2.53 - Unauthenticated IP Header Spoofing

2025-10-30 00:00
Jonas Benjamin Friedli

Strategic Overview

Status
Patched in 1.2.54
Affected Version
<= 1.2.53
CVSS
5.3Medium
Weakness type
CWE-693 · Protection Mechanism Failure
CVE
CVE-2025-12094
View all OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) vulnerabilities

At a glance

CVE-2025-12094 is a medium-severity Protection Mechanism Failure vulnerability in the OOPSpam Anti-Spam WordPress plugin, affecting versions <= 1.2.53. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.54; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.

Vulnerability Overview

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.

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, and no interaction from a victim user.

CWE-693: Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

Remediation

Update to version 1.2.54, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: OOPSpam Anti-Spam 1.2.54 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C