Ticket customer reassignment via missing per-ticket authorization
Published Aug 1, 2026 · Updated Aug 1, 2026
IDOR in WPManageNinja Fluent Support before 2.3.1 allows remote authenticated users to reassign any ticket's customer. The PUT /wp-json/fluent-support/v2/tickets/{ticket}/change-customer endpoint accepts a user-controlled customer ID without checking the agent's access to that ticket. A restricted support-agent account and REST nonce are required; exploitation changes the stored ticket-to-customer association even when normal ticket actions are denied.
Summary
What happened
IDOR in WPManageNinja Fluent Support before 2.3.1 allows remote authenticated users to reassign any ticket's customer. The PUT /wp-json/fluent-support/v2/tickets/{ticket}/change-customer endpoint accepts a user-controlled customer ID without checking the agent's access to that ticket. A restricted support-agent account and REST nonce are required; exploitation changes the stored ticket-to-customer association even when normal ticket actions are denied.
The record
- CVE
- CVE-2026-14197
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- Mahmudul Hasan Arif
- Product
- Fluent Support
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan authenticated ticket-customer reassignment proof of conceptfunctional · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo