CVE-2024-1640

Contact Form Builder Plugin: Multi Step Contact Form, Payment Form, Custom Contact Form Plugin by Bit Form <= 2.10.1 - Unauthenticated Insecure Direct Object Reference to Form Submission Alteration

2024-03-13 00:00
Lucio Sá

Strategic Overview

Status
Patched in 2.10.2
Affected Plugin
Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder
Affected Version
<= 2.10.1
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-1640
View all Bit Form – Contact Form, Payment Forms, Multi Step Forms, Calculator & Custom Form Builder vulnerabilities

At a glance

CVE-2024-1640 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Bit Form WordPress plugin, affecting versions <= 2.10.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.10.2; sites on affected versions should update now. Disclosed March 2024, reported by Lucio Sá.

Vulnerability Overview

The Contact Form Builder Plugin: Multi Step Contact Form, Payment Form, Custom Contact Form Plugin by Bit Form plugin for WordPress is vulnerable to unauthorized modification of data due to a insufficient user validation on the bitforms_update_form_entry AJAX action in all versions up to, and including, 2.10.1. This makes it possible for unauthenticated attackers to modify form submissions.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Bit Form <= 2.10.1 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Bit Form the fix is 2.10.2: builds <= 2.10.1 are affected, anything from 2.10.2 onward is not.

Remediation

Update to version 2.10.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: Bit Form 2.10.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-2024-1640https://www.wordfence.com/threat-intel/vulnerabilities/id/49ed7d6a-4a65-4efc-90e5-ffa5470d4011https://nvd.nist.gov/vuln/detail/CVE-2024-1640

Related records

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