CVE-2026-14372

Bit Form <= 3.1.1 - Authenticated (Subscriber+) Arbitrary File Deletion via '_old' Parameter

2026-07-08 21:29
Athiwat Tiprasaharn (Jitlada)

Strategic Overview

Status
Patched in 3.1.2
Affected Plugin
Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder
Affected Version
<= 3.1.1
CVSS
7.1High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-14372
View all Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder vulnerabilities

At a glance

CVE-2026-14372 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Bit Form WordPress plugin, affecting versions <= 3.1.1. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.1.2; sites on affected versions should update now. Disclosed July 2026, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the deleteFiles function in all versions up to, and including, 3.1.1 This makes it possible for authenticated attackers, with subscriber-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).

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 availability.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Bit Form <= 3.1.1 takes an account at Subscriber level or above. 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 3.1.2: builds <= 3.1.1 are affected, anything from 3.1.2 onward is not.

Remediation

Update to version 3.1.2, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Bit Form 3.1.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-14372https://www.wordfence.com/threat-intel/vulnerabilities/id/943668eb-0185-4029-9459-f99141bf84cfhttps://nvd.nist.gov/vuln/detail/CVE-2026-14372

Related records

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