CVE-2026-15209

JS Help Desk – AI-Powered Support & Ticketing System <= 3.1.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Cross-User Support Ticket Disclosure

2026-07-13 00:00
Sai Praneeth Koti

Strategic Overview

Status
Patched in 3.1.5
Affected Plugin
JS Help Desk – AI-Powered Support & Ticketing System
Affected Version
<= 3.1.4
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-15209
View all JS Help Desk – AI-Powered Support & Ticketing System vulnerabilities

At a glance

CVE-2026-15209 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the JS Help Desk WordPress plugin, affecting versions <= 3.1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.1.5; sites on affected versions should update now. Disclosed July 2026, reported by Sai Praneeth Koti.

Vulnerability Overview

The JS Help Desk – AI-Powered Support & Ticketing System plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.1.4. This is due to missing authorization checks on the ticket edit action, allowing any authenticated user to access tickets without verifying ownership or role. This makes it possible for authenticated attackers, with subscriber-level access and above, to view and edit arbitrary support tickets belonging to other users by manipulating the ticket ID parameter.

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 JS Help Desk <= 3.1.4 takes an account at Subscriber 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 JS Help Desk the fix is 3.1.5: builds <= 3.1.4 are affected, anything from 3.1.5 onward is not.

Remediation

Update to version 3.1.5, 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: JS Help Desk 3.1.5 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-15209https://www.wordfence.com/threat-intel/vulnerabilities/id/773be426-6fbc-49be-8a2a-5e794c58be8bhttps://nvd.nist.gov/vuln/detail/CVE-2026-15209

Related records

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