CVE-2025-7341

HT Contact Form Widget For Elementor Page Builder & Gutenberg Blocks & Form Builder. <= 2.2.1 - Unauthenticated Arbitrary File Deletion

2025-07-14 15:58
vgo0

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-269 · Improper Privilege Management
CVE
CVE-2025-7341
View all HT Contact Form – Drag & Drop Form Builder for WordPress vulnerabilities

At a glance

CVE-2025-7341 is a critical-severity Improper Privilege Management 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 vgo0.

Vulnerability Overview

The 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 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-269: Improper Privilege Management

HT Contact Form <= 2.2.1 carries this weakness at temp_file_delete(), and reaching it takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. 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?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. 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.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-7341https://www.wordfence.com/threat-intel/vulnerabilities/id/32da04ba-bee3-4fd3-b91b-57e588d5f4e4https://nvd.nist.gov/vuln/detail/CVE-2025-7341

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C