Download Contact Form 7 Widget For Elementor Page Builder \& Gutenberg BlocksWordPress extension · Hasthemes
CVE-2025-7341
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe HT Contact Form Widget For Elementor Page Builder & Gutenberg Blocks & Form Builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the temp_file_delete() function in all versions up to, and including, 2.2.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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe HT Contact Form Widget plugin for WordPress contains an arbitrary file deletion vulnerability in the temp_file_delete() function. The function lacks proper path validation, allowing unauthenticated attackers to supply path traversal sequences (e.g., ../../wp-config.php) to delete arbitrary files on the server. Deletion of critical files like wp-config.php can reset the WordPress installation and enable remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Download Contact Form 7 Widget For Elementor Page Builder \& Gutenberg BlocksWordPress extension
< 2.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins. Look for 'HT Contact Form Widget' or 'Hasthemes Download Contact Form 7 Widget For Elementor Page Builder & Gutenberg Blocks' and note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/ht-contact-form-widget/ or similar folder name.Affected if The installed version is lower than 2.2.2 (e.g., 2.2.1, 2.2.0, 1.x.x, or no version shown indicating an old release)
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the HT Contact Form Widget plugin shows as 'Active'. The vulnerability is exploitable even when the widget is not actively used on a page, as long as the plugin is enabled.Affected if The plugin is installed and activated on the WordPress site
-
Identify the vulnerable temp_file_delete functionAccess the site via FTP or file manager and locate the plugin PHP files. Search for the function named 'temp_file_delete' within the plugin directory. This function should contain file deletion logic without proper path validation.Affected if The temp_file_delete function exists in the plugin files and lacks sanitization checks for path traversal sequences (e.g., does not validate or block '../' in the file path)
-
Check if the vulnerable endpoint is accessibleInspect the plugin AJAX handlers or publicly accessible PHP files to determine if the temp_file_delete function can be called without authentication. Look for wp_ajax or wp_ajax_nopriv hooks registering the deletion action.Affected if The temp_file_delete function is hooked to an AJAX action accessible to unauthenticated users (wp_ajax_nopriv) or is callable without authentication checks
-
Inspect for signs of file deletionCheck for the existence of critical WordPress files: wp-config.php, .htaccess, and index.php in the site root directory. Also verify the /wp-content/ folder structure is intact.Affected if Critical files are missing or have been modified, or error logs in /wp-content/debug.log show attempted path traversal deletions
The environment is affected if the HT Contact Form Widget plugin is installed with a version lower than 2.2.2 and the temp_file_delete function is exposed without authentication, allowing path traversal deletion of arbitrary files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.2.2
Update the plugin to version 2.2.2 or later once available, which should include proper path validation and access controls in the temp_file_delete() function. Alternatively, disable the plugin until a patch is available.
2.2.2
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'HT Contact Form Widget For Elementor Page Builder & Gutenberg Blocks & Form Builder' plugin
- Check the current version number to confirm it is 2.2.1 or below
- If an update is available, click 'Update Now' to upgrade to version 2.2.2
- Alternatively, navigate to Dashboard > Updates and apply available updates
- After updating, verify the plugin version shows 2.2.2 under Plugins > Installed Plugins
- Consider reviewing the site to ensure the contact form functionality remains operational after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Download Contact Form 7 Widget For Elementor Page Builder \& Gutenberg Blocks
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7341 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data