WordPress security by component
OOPSpam Anti-Spam
Plugin description
OOPSpam Anti-Spam is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Mar 25, 2026; the highest CVE/CNA score is 7.1.
Plugin slug:
oopspam-anti-spamLatest vulnerability
CVE-2026-32544: OOPSpam Anti-Spam: Cross-site scripting
OOPSpam Anti-Spam is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is n/a through <= 1.2.62.
| Safe version |
|
||
|---|---|---|---|
| Mar 25, 2026 |
CVE-2026-32544
OOPSpam Anti-Spam: Cross-site scripting
OOPSpam Anti-Spam is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is n/a through <= 1.2.62.
|
1.2.63 |
CVE7.1
NVDPending
|
| Oct 31, 2025 |
CVE-2025-12094
OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA): A security weakness
OOPSpam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Jul 11, 2023 |
CVE-2023-35913
Oopspam Anti Spam: Cross-site request forgery
Oopspam Anti Spam is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVD8.8
|
| Mar 23, 2023 |
CVE-2023-22716
Oopspam Anti Spam: Cross-site scripting
Oopspam Anti Spam is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE5.9
NVD4.8
|