CVE-2023-41952

Contact Form for Plugin by Fluent Forms <= 5.0.8 - Insecure Direct Object Reference

2023-09-08 00:00
Revan Arifio

Strategic Overview

Status
Patched in 5.0.9
Affected Plugin
Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder
Affected Version
< 5.0.9
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-41952
View all Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder vulnerabilities

At a glance

CVE-2023-41952 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Fluent Forms WordPress plugin, affecting versions < 5.0.9. 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 5.0.9; sites on affected versions should update now. Disclosed September 2023, reported by Revan Arifio.

Vulnerability Overview

The Contact Form for Plugin by Fluent Forms plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.0.8 via the addIsRenderableFilter() function due to missing validation on the publication status of a form. This makes it possible for users to render and submit forms when the form is in an 'unpublished' state.

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

Fluent Forms < 5.0.9 carries this weakness at unpublished, 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 Fluent Forms the fix is 5.0.9: builds < 5.0.9 are affected, anything from 5.0.9 onward is not.

Remediation

Update to version 5.0.9, 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: Fluent Forms 5.0.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-41952https://www.wordfence.com/threat-intel/vulnerabilities/id/20f31e48-0dbb-498a-a400-681cacea7c9chttps://nvd.nist.gov/vuln/detail/CVE-2023-41952

Related records

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