Description
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.2.8 via the 'transaction' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to brute-force valid transaction hashes and view sensitive payment receipt data including customer name, email address, billing address, order items, payment method, and payment status belonging to other users. Because submission ID, form ID, and transaction creation time are either observable or guessable by an attacker, the effective brute-force space is bounded to approximately 900 candidates per second per (submission, form) pair, making exploitation practical without any prior authentication or account.
Published: 2026-07-31
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw is an insecure direct object reference in the 'transaction' parameter of the Fluent Forms plugin. Because the plugin accepts a user-controlled value without validation, an unauthenticated attacker can brute‑force transaction identifiers and retrieve full payment receipt data, including customer names, emails, billing addresses, order items, payment methods and status belonging to other users. This exposes highly sensitive personal and transactional information.

Affected Systems

WordPress sites using the WP Manage Ninja "Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder" plugin, any version up to and including 6.2.8. The vulnerability is tied to the payment handling components referenced in the plugin source code.

Risk and Exploitability

The CVSS score is 5.3, indicating a medium severity issue. The EPSS value is less than 1 %, suggesting that exploit attempts are rare, and the vulnerability is not listed in the CISA KEV catalog. Nonetheless, the attack vector is practically viable: an attacker can send unauthenticated HTTP requests to the plugin’s transaction endpoint, leveraging the fact that submission IDs, form IDs, and creation times are observable or guessable. This reduces the brute‑force search space to roughly 900 candidates per second per (submission, form) pair, making exploitation feasible without any prior authentication or user account.

Generated by OpenCVE AI on August 2, 2026 at 04:18 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Fluent Forms to version 6.2.9 or later, which removes the insecure direct object reference in the transaction handling code
  • If an upgrade is not immediately possible, restrict the PaymentHandler and related shortcodes to users with the 'administrator' role by adding capability checks or applying basic authentication at the web‑server level
  • Audit any custom code that interacts with the 'transaction' parameter to ensure it performs proper authentication and validation before processing requests

Generated by OpenCVE AI on August 2, 2026 at 04:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 01 Aug 2026 00:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 31 Jul 2026 11:45:00 +0000

Type Values Removed Values Added
First Time appeared Wordpress
Wordpress wordpress
Wpmanageninja
Wpmanageninja fluent Forms
Vendors & Products Wordpress
Wordpress wordpress
Wpmanageninja
Wpmanageninja fluent Forms

Fri, 31 Jul 2026 10:30:00 +0000

Type Values Removed Values Added
Description 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.2.8 via the 'transaction' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to brute-force valid transaction hashes and view sensitive payment receipt data including customer name, email address, billing address, order items, payment method, and payment status belonging to other users. Because submission ID, form ID, and transaction creation time are either observable or guessable by an attacker, the effective brute-force space is bounded to approximately 900 candidates per second per (submission, form) pair, making exploitation practical without any prior authentication or account.
Title Fluent Forms <= 6.2.8 - Unauthenticated Sensitive Information Exposure via Insecure Direct Object Reference and Weak Transaction Hash in 'transaction' Parameter
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}


Subscriptions

Wordpress Wordpress
Wpmanageninja Fluent Forms
cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-07-31T23:25:22.575Z

Reserved: 2026-07-27T14:45:05.088Z

Link: CVE-2026-17567

cve-icon Vulnrichment

Updated: 2026-07-31T23:25:17.428Z

cve-icon NVD

Status : Deferred

Published: 2026-07-31T11:17:05.697

Modified: 2026-08-12T21:00:37.147

Link: CVE-2026-17567

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-02T04:30:13Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key