HT Contact Form Widget For Elementor Page Builder & Gutenberg Blocks & Form Builder. <= 2.2.1 - Directory Traversal to Arbitrary File Move
Strategic Overview
- Status
- Patched in 2.2.2
- Affected Plugin
- HT Contact Form – Drag & Drop Form Builder for WordPress
- Affected Version
<= 2.2.1- CVSS
- 9.1Critical
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-7360
At a glance
CVE-2025-7360 is a critical-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the HT Contact Form WordPress plugin, affecting versions <= 2.2.1. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.2.2; sites on affected versions should update now. Disclosed July 2025, reported by Phat RiO.
Vulnerability Overview
The HT Contact Form Widget For Elementor Page Builder & Gutenberg Blocks & Form Builder plugin for WordPress is vulnerable to arbitrary file moving due to insufficient file path validation in the handle_files_upload() function in all versions up to, and including, 2.2.1. This makes it possible for unauthenticated attackers to move arbitrary files on the server, which can easily lead to remote code execution when the right file is moved (such as wp-config.php).
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
HT Contact Form <= 2.2.1 carries this weakness at handle_files_upload(), and reaching it takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For HT Contact Form the fix is 2.2.2: builds <= 2.2.1 are affected, anything from 2.2.2 onward is not.
Remediation
Update to version 2.2.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to HT Contact Form: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: HT Contact Form 2.2.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in HT Contact Form – Drag & Drop Form Builder for WordPress
- 9.8CVE-2025-7340: HT Contact Form Widget… Arbitrary File Upload
CVE-2025-7340 - 9.1CVE-2025-7341: HT Contact Form Widget… Arbitrary File Deletion
CVE-2025-7341 - 7.2CVE-2026-7052: HT Contact Form <= 2.8.2 Stored Cross-Site Scripting
CVE-2026-7052 - 7.2CVE-2026-42728: HT Contact Form Stored XSS
CVE-2026-42728 - 6.6CVE-2025-54015: HT Contact Form 7 <= 2.0.0 Local File Inclusion
CVE-2025-54015 - 6.4CVE-2025-24726: HT Conctact Form 7 <= 1.2.1 Stored XSS
CVE-2025-24726 - 5.3CVE-2026-14206: HT Contact Form <= 2.9.2 Information Exposure
CVE-2026-14206 - 4.3CVE-2023-0484: Contact Form 7 Widget For Elementor… CSRF
CVE-2023-0484
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C