CVE-2026-14372 json
Bit Form <= 3.1.1 - Authenticated (Subscriber+) Arbitrary File Deletion via '_old' Parameter
published 4mo ago modified 4mo ago also EUVD-2026-42564
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
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).
Is CVE-2026-14372 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
1.06% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H |
Affected products
- bitpressadmin Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/943668eb-0185-4029-9459-f99141bf84cf?source=cve
- plugins.trac.wordpress.org /browser/bit-form/tags/3.1.1/includes/Core/Util/FileHandler.php#L129
- plugins.trac.wordpress.org /browser/bit-form/tags/3.1.1/includes/Core/Form/FormManager.php#L1039
- plugins.trac.wordpress.org /browser/bit-form/tags/3.1.1/includes/Core/Form/FormManager.php#L1044
- plugins.trac.wordpress.org /browser/bit-form/tags/3.1.1/includes/Frontend/Ajax/FrontendAjax.php#L87
- plugins.trac.wordpress.org /browser/bit-form/tags/3.1.1/includes/Admin/Form/Helpers.php#L302
- plugins.trac.wordpress.org /browser/bit-form/trunk/includes/Core/Util/FileHandler.php#L129
- plugins.trac.wordpress.org /browser/bit-form/trunk/includes/Core/Form/FormManager.php#L1039
- plugins.trac.wordpress.org /browser/bit-form/trunk/includes/Core/Form/FormManager.php#L1044
- plugins.trac.wordpress.org /browser/bit-form/trunk/includes/Frontend/Ajax/FrontendAjax.php#L87
- plugins.trac.wordpress.org /browser/bit-form/trunk/includes/Admin/Form/Helpers.php#L302
- plugins.trac.wordpress.org /changeset/3598554/bit-form/trunk/includes/Core/Form/FormManager.php
- plugins.trac.wordpress.org /changeset?old_path=%2Fbit-form/tags/3.1.1&new_path=%2Fbit-form/tags/3.1.2
Sources
- CVE List CVE-2026-14372
- NVD CVE-2026-14372
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.