WordPress security by component
Conditional Fields for Contact Form 7
Plugin description
Conditional Fields for Contact Form 7 is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published May 04, 2026; the highest CVE/CNA score is 8.7.
Plugin slug:
cf7-conditional-fieldsLatest vulnerability
CVE-2026-25863: Conditional Fields for Contact Form 7: A security weakness
Conditional Fields for Contact Form 7 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. The published affected range is < 2.7.3.
| Safe version |
|
||
|---|---|---|---|
| May 04, 2026 |
CVE-2026-25863
Conditional Fields for Contact Form 7: A security weakness
Conditional Fields for Contact Form 7 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. The published affected range is < 2.7.3.
|
2.7.3 |
CVE8.7
NVDPending
|
| Dec 09, 2024 |
CVE-2023-47838
Conditional Fields for Contact Form 7: A security weakness
Conditional Fields for Contact Form 7 is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Oct 29, 2024 |
CVE-2024-50412
Conditional Fields for Contact Form 7: Cross-site scripting
Conditional Fields for Contact Form 7 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
NVDPending
|
| Jul 20, 2024 |
CVE-2024-5804
Conditional Fields for Contact Form 7: Cross-site request forgery
Conditional Fields for Contact Form 7 is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE4.3
NVDPending
|