Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site with vulnerable CF7 signature field
-
DeliveryCraft PHP payload named shell.php-
-
ExploitSubmit via extcf7_submit upload
-
Executionsanitize_file_name bypass writes shell.php
-
PersistRequest uploaded file to execute
-
ImpactRemote code execution as web user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the target WordPress site to run Extensions For CF7 version 3.4.5 or earlier AND to have a Contact Form 7 form that uses the plugin's signature field, since the flaw lives in that field's validation_filter() reached through the extcf7_submit function. The attack succeeds against such configurations because file extension, MIME type, and size validation are all missing, the upload directory lacks PHP-execution guards, and sanitize_file_name() can be bypassed (shell.php- becomes shell.php); no authentication (PR:N) and no user interaction (UI:N) are needed. The main limiting factor is that a form must actually expose the signature field and the server must be configured to execute PHP in the upload path - sites not using the signature feature are not exposed via this vector. |
| Impact | This is a genuine high-priority vulnerability, not an inflated CVSS score. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes remote, low-complexity, unauthenticated exploitation with high confidentiality, integrity, and availability impact, which is fully consistent with the CWE-434 arbitrary-file-upload-to-RCE described: a signature field's validation_filter() lacks extension, MIME, and size checks, the upload directory has no PHP-execution guard, and a sanitize_file_name() bypass restores 'shell.php-' to 'shell.php'. All three preconditions chain into unauthenticated webshell execution, so the technical impact rating is well supported. The key tempering signals are the absence of hard exploitation data: no EPSS score was supplied, the vulnerability is NOT on CISA KEV, and no public POC is referenced - so there is no public exploit identified at time of analysis and no evidence of active or automated exploitation yet. No SSVC decision record was provided. Net: treat as urgent patching priority because the flaw class (unauthenticated file upload in a WordPress plugin) is historically a prime target for mass automated scanning once a POC emerges, but current real-world exploitation is unconfirmed rather than demonstrated. |
| Exploit ScenarioDerived | An unauthenticated attacker locates a WordPress site running Extensions For CF7 <= 3.4.5 with a Contact Form 7 form that uses the signature field, then submits the form via the extcf7_submit function with a malicious PHP file named to bypass sanitize_file_name() (e.g. 'shell.php-'). Because extension, MIME, and size validation are missing and the upload directory has no PHP-execution guard, the file lands as an executable 'shell.php' and the attacker requests its URL to run arbitrary code. No public exploit is identified at time of analysis, but the bug class is trivially weaponizable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unauthenticated arbitrary file upload in the WordPress plugin Extensions For CF7 (Contact Form 7 Database, Conditional Fields and Redirection) versions up to and including 3.4.5 allows remote attackers to write attacker-controlled files into the site's upload directory through the plugin's signature field, with remote code execution as the likely outcome. The flaw is reachable via the extcf7_submit function without authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) but only on sites that have a Contact Form 7 form actually using the plugin's signature field; sites not exposing that field are not reachable through this vector. At time of analysis no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), and the vendor has released a fix in version 3.4.6, so the exposure window is bounded by how quickly affected sites update.
RemediationAI
Upgrade the Extensions For CF7 plugin to version 3.4.6 or later, which the vendor released as the fix (Trac changeset 3727009 comparing tags 3.4.5 and 3.4.6); verify the update actually applied, since WordPress plugin auto-updates may be disabled on managed or hardened installations. If immediate patching is not possible, the most effective compensating control is to prevent PHP execution in the WordPress uploads directory - for example an Apache .htaccess rule removing the PHP handler (php_flag engine off / RemoveHandler) or the equivalent nginx location block denying .php files under wp-content/uploads - with the trade-off that misconfigured rules can break legitimate plugins that execute scripts from uploads, and the control fails on servers that ignore .htaccess. A second mitigation is to remove or disable the plugin's signature field from all Contact Form 7 forms, which eliminates the vulnerable code path entirely at the cost of losing the signature-capture feature. Site operators can also temporarily deactivate the plugin if the signature functionality is not in use, and front-end WAF rules blocking multipart uploads that carry .php or .php- style filenames to the extcf7_submit endpoint add defense in depth but are bypassable via encoding tricks and should not be relied on alone. After patching, review wp-content/uploads for unexpected PHP files and any recently modified files, since a successful pre-patch exploitation would have left attacker-controlled payloads behind.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is CWE-434 (Unrestricted Upload of File with Dangerous Type) rooted in the plugin's signature-field handling. The upload path is reached through extcf7_submit, and the signature field's validation_filter() performs no file extension check, no MIME type check, and no file size check, so any file content submitted with the signature field is accepted. Compounding factors make execution likely rather than merely possible: the plugin stores uploads in a directory without PHP-execution guards, and a sanitize_file_name() bypass means a name such as shell.php- is normalized to shell.php, restoring an executable extension that would otherwise have been stripped. The relevant code paths are visible in the plugin source at class.cf7-signature.php (validation_filter and surrounding logic), class.form-data-store.php, and class.cf7-extensions.php for the 3.4.5 tag. The CPE cpe:2.3:a:htplugins:extensions_for_cf7_(contact_form_7_database,_conditional_fields_and_redirection):*:*:*:*:*:*:*: identifies the WordPress plugin from vendor htplugins as the affected component, and because this is a WordPress plugin vulnerability the practical risk depends on the site's web server being configured to execute PHP inside the uploads path - a common default on Apache/mod_php and some other stacks. The attack is fully remote and requires no credentials or user interaction, but it does require the target form to expose the signature field, which is the principal limiting precondition noted in the independent assessment.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Unauthenticated (PR:N) remote (AV:N) file upload with no user interaction and low complexity yields webshell RCE, giving full C/I/A impact on the host.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection) plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 3.4.5 via the extcf7_submit function. This is due to missing file extension, MIME type, and size validation in the signature field's validation_filter(), combined with the absence of PHP-execution guards in the upload directory and a sanitize_file_name() bypass that converts shell.php- into shell.php. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible.
Articles & Coverage 1
Executive ViewAI
The WordPress plugin Extensions For CF7 (Contact Form 7 Database, Conditional Fields and Redirection), versions up to and including 3.4.5, contains a critical unauthenticated file upload flaw that can allow an outside attacker to place and execute code on any affected website. The exposure applies only to sites where a Contact Form 7 form actually uses the plugin's signature field, so leadership should treat this as a targeted but potentially total site-takeover risk for those properties, with follow-on consequences for customer data, brand trust, and hosted content. A vendor fix exists in version 3.4.6, meaning organizational risk is now driven almost entirely by patch latency rather than by an unknown remedy.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-96041
GHSA-fjhx-3cm7-whvf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB