# CVE-2025-12094: Security feature bypass in OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA)

> Unauthenticated attackers can spoof IP addresses via forwarded headers to bypass IP-based security controls and rate limiting in the OOPSpam WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-4qw6-7g5m-4mvh

## What is CVE-2025-12094?

CVE-2025-12094 is a medium-severity vulnerability in OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA), published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2025-12094?


## How do I fix CVE-2025-12094?

No fix has been published for CVE-2025-12094 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12094 being exploited?

There is no known exploitation of CVE-2025-12094 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12094 and fix it if it is affected.

What it is: CVE-2025-12094 is a medium-severity vulnerability in OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA), published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12094 in the wild and no public exploit code.

Affected product: OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12094/ (Markdown: https://insights.sbomify.com/CVE-2025-12094/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12094
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12094
- OSV: https://osv.dev/vulnerability/CVE-2025-12094

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12094/
Summaries are generated and may contain mistakes; the official description above is the record.