oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) vulnerabilities
Plugin slug oopspam-anti-spam · 4 known vulnerabilities · latest disclosed 2026-03-23 · WordPress.org page
Every listed vulnerability has a fix. Version 1.2.63 or later is not affected by any of them. If your site runs an older version, update it.
1 of 4 rated high or critical (CVSS 7 or more).
Known vulnerabilities in oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA)
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 7.2 | <= 1.2.62 | 1.2.63 | CVE-2026-32544 | 2026-03-23 | Advisory |
| Medium 5.3 | <= 1.2.53 | 1.2.54 | CVE-2025-12094 | 2025-10-30 | Advisory |
| Medium 5.4 | < 1.1.45 | 1.1.45 | CVE-2023-35913 | 2023-06-21 | Advisory |
| Medium 5.5 | <= 1.1.35 | 1.1.36 | CVE-2023-22716 | 2023-01-17 | Advisory |
Check if a site is affected
Enter a site address to see which version of oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) plugin safe to use?
All 4 known issues are fixed in current versions (1.2.63 or later). Keeping it updated is what matters.
How do I check which version of oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.