Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Network-reachable form submission with no auth (AV:N/PR:N), but deletion only fires when an admin views the entry (UI:R); arbitrary file deletion yields I:H/A:H with no direct read (C:N).
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Lifecycle Timeline
2DescriptionCVE.org
The Database for Contact Form 7, WPforms, Elementor forms plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the view_page function in all versions up to, and including, 1.5.1. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Successful exploitation requires an administrator to view or edit the poisoned form entry, at which point PHP's bracket parser reshapes the attacker-crafted JSON key to bypass the stored-path isset check and trigger deletion of the traversal-specified file.
AnalysisAI
Arbitrary file deletion in the Database for Contact Form 7, WPforms, Elementor forms WordPress plugin (versions ≤1.5.1) allows remote unauthenticated attackers to poison form entries with traversal payloads that, when later viewed by an administrator, delete arbitrary server files and can be escalated to remote code execution by removing wp-config.php. Reported by Wordfence with publicly available exploit code exists via the Wordfence advisory; no public exploit identified at time of analysis as weaponized in-the-wild attacks, and the issue is not in CISA KEV.
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The vulnerable plugin Database for Contact Form 7, WPforms, Elementor forms (contact-form-entries) version ≤1.5.1 must be installed and active on a WordPress site with at least one form whose submissions are routed through the plugin's entry storage. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H) accurately reflects a two-stage attack: anyone on the internet can plant the payload (PR:N), but the destructive action only fires when an administrator opens the poisoned entry (UI:R), which is highly likely on any active WordPress site that triages submissions. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An unauthenticated attacker submits a contact form on a vulnerable WordPress site, embedding a crafted field name with bracket/JSON-key traversal payload pointing at wp-config.php; the entry is stored without immediate effect. When a site administrator later opens the entry in the Contact Form Entries admin UI, the view_page handler resolves the poisoned key, bypasses the isset() guard, and unlinks wp-config.php, causing WordPress to enter the installation wizard so the attacker can re-point the site to a database they control and gain full RCE - a primitive consistent with the technical detail published in the Wordfence advisory. |
| Remediation | Upstream fix available (changeset 3578556); released patched version not independently confirmed beyond '> 1.5.1', so administrators should update the Contact Form Entries plugin to the latest available release from the WordPress.org plugin repository as soon as it is published and verify the installed version is greater than 1.5.1. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Immediately disable or uninstall affected plugin versions (≤1.5.1); audit server logs for suspicious form submissions and file deletion attempts; if operations permit, temporarily disable form submission functionality. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
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
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
NetAlertX (formerly PiAlert) versions 23.01.14 through 24.x before 24.10.12 allow unauthenticated command injection thro
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-38104
GHSA-m735-jrv9-j3fc