CVE-2026-119213

Fluent Support <= 2.4.7 — Unauthenticated Limited Modification of Linked Customer Profile Fields via Fluent Forms Feed

2026-11-06 13:47
Santh

Strategic Overview

Status
Patched in 2.5.0
Affected Version
<= 2.4.7
CVSS
3.7Low
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-119213
View all Fluent Support – Helpdesk & Customer Support Ticket System vulnerabilities

At a glance

CVE-2026-119213 is a low-severity Authorization Bypass Through User-Controlled Key vulnerability in the Fluent Support WordPress plugin, affecting versions <= 2.4.7. It carries a CVSS score of 3.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 2.5.0; sites on affected versions should update now. Disclosed November 2026, reported by Santh.

Vulnerability Overview

The Fluent Support – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to unauthenticated modification of a linked customer's stored profile fields in versions up to, and including, 2.4.7 Its first-party Fluent Forms integration (FeedIntegration::notify()) opens a ticket from each public form submission and, for a logged-out submitter, resolves the submitted email to an existing WordPress account via get_user_by('email', ...) without verifying the submitter controls that address, then passes the attacker-supplied data to Customer::maybeCreateCustomer(). This makes it possible for unauthenticated attackers to overwrite a limited set of a registered customer's stored profile fields where an administrator has enabled a FluentSupport feed on a public form. The email address, role and status are never changed; first and last name are overwritten only when the target user has no name set in user meta; and other fields (title, address, city, state, zip, country) are writable only where an administrator has mapped them in the feed.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Fluent Support <= 2.4.7 carries this weakness at email, 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 Support the fix is 2.5.0: builds <= 2.4.7 are affected, anything from 2.5.0 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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