CVE-2024-9700

Forminator Forms – Contact Form, Payment Form & Custom Form Builder <= 1.36.0 - Insecure Direct Object Reference to Submission Manipulation

2024-10-30 00:00
Vijaysimha Reddy (vijaysimha)

Strategic Overview

Status
Patched in 1.36.1
Affected Plugin
Forminator Forms – Contact Form, Payment Form & Custom Form Builder
Affected Version
<= 1.36.0
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-9700
View all Forminator Forms – Contact Form, Payment Form & Custom Form Builder vulnerabilities

At a glance

CVE-2024-9700 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Forminator Forms WordPress plugin, affecting versions <= 1.36.0. 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 1.36.1; sites on affected versions should update now. Disclosed October 2024, reported by Vijaysimha Reddy (vijaysimha).

Vulnerability Overview

The Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.36.0 via the submit_quizzes() function due to missing validation on the 'entry_id' user controlled key. This makes it possible for unauthenticated attackers to modify other user's quiz 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

Forminator Forms <= 1.36.0 carries this weakness at entry_id, and reaching it takes a caller who can reach the endpoint. 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 Forminator Forms the fix is 1.36.1: builds <= 1.36.0 are affected, anything from 1.36.1 onward is not.

Remediation

Update to version 1.36.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Forminator Forms 1.36.1 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-9700https://www.wordfence.com/threat-intel/vulnerabilities/id/fbed35ca-1630-46a4-8b1f-60cc7216f294https://nvd.nist.gov/vuln/detail/CVE-2024-9700

Related records

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