Spam Protect for Contact Form 7 · Security record
Is Spam Protect for Contact Form 7 safe?
No known vulnerability affects the current version (1.2.10). 2 issues were found in earlier versions and fixed, the latest disclosed on Mar 20, 2026.
Checked today against the WPVulnerability database, for version 1.2.10.
How it’s looked after
- Last release
- Feb 6, 2026 (9 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 6.8.12 (current: 7.1)
- Support resolved
- 1 of 1 threads in two months
- Active installs
- 10K+
2 known vulnerabilities
- 1 medium
- 1 not rated
None affects the current version.
Every known vulnerability in Spam Protect for Contact Form 7
Newest first, with any that affect the current version at the top.
Fixed in 1.2.10 · CVE-2026-32496 · Mar 20, 2026 · Wordfence
Fixed in 1.2.10 · CVE-2026-1540 · Mar 12, 2026 · Wordfence
Questions about Spam Protect for Contact Form 7’s security
Is Spam Protect for Contact Form 7 safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Spam Protect for Contact Form 7 updated: most attacks target sites that haven’t updated.
Does Spam Protect for Contact Form 7 have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep Spam Protect for Contact Form 7 up to date.
Is Spam Protect for Contact Form 7 still maintained?
Its last release was 9 months ago. Its authors resolved 1 of the 1 support threads opened in the last two months.
Is Spam Protect for Contact Form 7 compatible with the latest WordPress?
Spam Protect for Contact Form 7’s readme says it’s tested up to WordPress 6.8.12, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.