CF7 to Webhook · Security record
Is CF7 to Webhook safe?
No known vulnerability affects the current version (5.1.0). 1 issue was found in earlier versions and fixed, the latest disclosed on Jun 17, 2026.
Checked 4 days ago against the WPVulnerability database, for version 5.1.0.
How it’s looked after
- Last release
- Jun 5, 2026 (5 months ago)
- Releases in the last year
- 3
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 30K+
1 known vulnerability
- 1 high
None affects the current version.
Every known vulnerability in CF7 to Webhook
Newest first, with any that affect the current version at the top.
Fixed in 5.0.1 · CVE-2026-11395 · Jun 17, 2026 · Wordfence
Questions about CF7 to Webhook’s security
Is CF7 to Webhook safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep CF7 to Webhook updated: most attacks target sites that haven’t updated.
Does CF7 to Webhook have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep CF7 to Webhook up to date.
Is CF7 to Webhook still maintained?
Yes. Its last release was 5 months ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is CF7 to Webhook compatible with the latest WordPress?
CF7 to Webhook’s readme says it’s tested up to WordPress 6.9.11, 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.