CVE-2024-7782

Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder 2.0 - 2.13.4 - Authenticater (Administrator+) Arbitrary File Deletion

2024-08-19 14:58
TANG Cheuk Hei (siunam)

Strategic Overview

Status
Patched in 2.13.5
Affected Version
2.0 – 2.13.4
CVSS
8.7High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2024-7782
View all Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder vulnerabilities

At a glance

CVE-2024-7782 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Bit Form WordPress plugin, affecting versions 2.0 – 2.13.4. It carries a CVSS score of 8.7 (reachable over the network; low attack complexity; high integrity, availability impact). The issue is fixed in version 2.13.5; sites on affected versions should update now. Disclosed August 2024, reported by TANG Cheuk Hei (siunam).

Vulnerability Overview

The Contact Form by Bit Form: Multi Step Form, Calculation Contact Form, Payment Contact Form & Custom Contact Form builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the iconRemove function in versions 2.0 to 2.13.4. This makes it possible for authenticated attackers, with Administrator-level access and above, 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 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')

Reaching this weakness in Bit Form 2.0 – 2.13.4 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 Bit Form the fix is 2.13.5: builds 2.0 – 2.13.4 are affected, anything from 2.13.5 onward is not.

Remediation

Update to version 2.13.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Bit Form: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Bit Form 2.13.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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