CVE-2025-12094 MEDIUM

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

Vendor Oopspam
Product OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA)
Weakness CWE-693
Published October 31, 2025
Last update April 8, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The OOPSpam Anti-Spam plugin for WordPress contains an integrity vulnerability affecting versions up to 1.2.53. An attacker on the network can modify data or content without authentication or user interaction. The vulnerability has low integrity impact and does not affect confidentiality or availability. Site administrators should update to a version newer than 1.2.53.

What an attacker can do

03Attacker Capabilities

Modify form submissions, comments, or plugin data without authentication.

Potential impact on your site

04Site Impact

Spam protection may be bypassed or form/comment data altered by attackers.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

October 31, 2025 CVE published
April 8, 2026 Record updated