CVE-2025-13748

Fluent Forms <= 6.1.7 - Unauthenticated Insecure Direct Object Reference to Payment Status Tampering via submission_id

2025-12-05 18:10
Md. Moniruzzaman Prodhan (NomanProdhan)

Strategic Overview

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

At a glance

CVE-2025-13748 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Fluent Forms WordPress plugin, affecting versions <= 6.1.7. 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 6.1.8; sites on affected versions should update now. Disclosed December 2025, reported by Md. Moniruzzaman Prodhan (NomanProdhan).

Vulnerability Overview

The Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.1.7 via the 'submission_id' parameter due to missing validation on a user controlled key within the confirmScaPayment() function. This makes it possible for unauthenticated attackers to mark arbitrary submissions as failed via crafted requests to the endpoint granted they can guess or enumerate a valid submission identifier.

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 <= 6.1.7 carries this weakness at submission_id, and reaching it 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 Fluent Forms the fix is 6.1.8: builds <= 6.1.7 are affected, anything from 6.1.8 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-13748https://www.wordfence.com/threat-intel/vulnerabilities/id/c2aee799-4e4c-4a41-8b76-e2ad576fe2e2https://nvd.nist.gov/vuln/detail/CVE-2025-13748

Related records

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