Download Contact Form 7 Widget For Elementor Page Builder \& Gutenberg BlocksWordPress extension · Hasthemes
CVE-2025-7340
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 uploads due to missing file type validation in the temp_file_upload() function in all versions up to, and including, 2.2.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 upload vulnerability in the temp_file_upload() function. The function lacks proper file type validation, allowing unauthenticated attackers to upload any file type to the server. This unrestricted upload capability can be leveraged to upload malicious PHP files and achieve 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.
-
Verify the plugin is installedCheck the WordPress plugins directory at wp-content/plugins/ for a folder named 'ht-contact-form-widget' or 'download-contact-form-7-widget' or check via WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the plugins directory
-
Determine the installed versionOpen the main plugin PHP file (usually ht-contact-form-widget.php) and locate the 'Version' header in the plugin comments, or check the version in WordPress admin plugin listAffected if Version is less than 2.2.2 (e.g., 2.2.1, 2.2.0, or any version up to 2.2.1)
-
Check if the temp_file_upload endpoint is accessibleTest accessing the upload endpoint via curl or browser: POST request to /wp-admin/admin-ajax.php?action=temp_file_upload (no authentication required for this CVE)Affected if The endpoint responds and accepts file uploads without authentication validation
-
Inspect uploads directory for suspicious filesReview contents of wp-content/uploads/ and subdirectories for unexpected file types such as .php, .phtml, .exe, .js, or other executable extensions that were not intentionally uploadedAffected if Unexpected executable files (.php, .phtml, .js) are present in uploads that you did not intentionally place there
You are affected if the HT Contact Form Widget plugin is installed with any version below 2.2.2, as the unauthenticated file upload vulnerability is present in all prior versions.
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 a version beyond 2.2.1 when available, or disable the plugin until a patch is released. Additionally, configure the web server to prevent execution of uploaded files in the upload directories.
2.2.2
- Backup your WordPress site database and files before performing any updates
- Navigate to WordPress admin dashboard > Plugins
- Locate 'HT Contact Form Widget For Elementor Page Builder & Gutenberg Blocks' in the installed plugins list
- Click 'Update now' to update the plugin to version 2.2.2
- After updating, verify the plugin version shows 2.2.2 in the plugins list
- Check that the admin/Includes/Services/FileManager.php file has been updated with the patch that adds file type validation
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
- Consultation3.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 $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7340 — 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-7340 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