CVE-2026-14197

Fluent Support – Helpdesk & Customer Support Ticket System < 2.3.1 - Authenticated (Custom role+) Insecure Direct Object Reference

2026-08-01 00:00
Mustafa Ahmed

Strategic Overview

Status
Patched in 2.3.1
Affected Plugin
Fluent Support – Helpdesk & Customer Support Ticket System
Affected Version
< 2.3.1
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-14197
View all Fluent Support – Helpdesk & Customer Support Ticket System vulnerabilities

At a glance

CVE-2026-14197 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Fluent Support WordPress plugin, affecting versions < 2.3.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom role level or above. The issue is fixed in version 2.3.1; sites on affected versions should update now. Disclosed August 2026, reported by Mustafa Ahmed.

Vulnerability Overview

The Fluent Support – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to 2.3.1 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with custom role-level access and above, to perform an unauthorized action.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Fluent Support < 2.3.1 takes an account at Custom role level or above. 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 Support the fix is 2.3.1: builds < 2.3.1 are affected, anything from 2.3.1 onward is not.

Remediation

Update to version 2.3.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: Fluent Support 2.3.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-2026-14197https://www.wordfence.com/threat-intel/vulnerabilities/id/b3ae17c3-9f65-4855-aed6-64d3ccb2ff0bhttps://nvd.nist.gov/vuln/detail/CVE-2026-14197

Related records

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