CVE-2026-119213 · Package
NO FIX YET · SEE WHAT TO DO
The Fluent Support helpdesk plugin for WordPress, up to and including 2.4.7, lets anyone who submits a public Fluent Forms form overwrite some stored profile fields of an existing customer whose email they supplied. The email, role and status cannot be changed; only name fields with no value set, and address fields an administrator mapped in the feed, can be altered.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running Fluent Support up to and including 2.4.7 where an administrator has attached a FluentSupport feed to a public Fluent Forms form. Sites without that feed configured, or without the plugin, are not exposed through this path. The attack needs no account, but only changes profile fields of existing WordPress users.
Not affected if no-fluentsupport-feed, plugin-not-installed, version-2.4.8-or-later
Who cares fluent-forms, fluent-support, self-hosted, wordpress
wp plugin get fluent-support --field=version2.4.7 are affected, but no fixed version is given)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.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.