WordPress plugin · cf7-conditional-fields
Is Conditional Fields for Contact Form 7 safe?
Safe on 2.8.3 or newer.
The current version, 2.8.3, is past every affected range on record (3 of 4 records list one; 1 doesn’t, so check it below). Keep it updated and you’re clear of them.
- Flaws on record
- 4
- High or critical
- 1
- Exploited
- none
- Current version
- 2.8.3
- Last updated
- Oct 21, 2026
- Active installs
- 100,000+
Every recorded flaw
- May 4, 2026Conditional Fields for Contact Form 7 WordPress plugin through version 2.7.2 contains an uncontrolled resource consumption vulnerability in the Wpcf7cfMailParseCVE-2026-25863 · reported by VulnCheckHigh 8.7
- Dec 9, 2024Conditional Fields for Contact Form 7: Missing AuthorizationCVE-2023-47838 · affects up to 2.4.1 · reported by PatchstackMedium 4.3
- Oct 29, 2024Conditional Fields for Contact Form 7: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2024-50412 · affects up to 2.4.15 · reported by PatchstackMedium 5.9
- Jul 19, 2024Conditional Fields for Contact Form 7: Cross-Site Request ForgeryCVE-2024-5804 · affects up to 2.4.13 · reported by WordfenceMedium 4.3
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.