CVE-2026-103079

JS Help Desk – AI-Powered Support & Ticketing System <= 4.0.0 - Authenticated (Subscriber+) Insecure Direct Object Reference

2026-10-05 08:52
Rasyid Abdi Gantoro

Strategic Overview

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

At a glance

CVE-2026-103079 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the JS Help Desk WordPress plugin, affecting versions <= 4.0.0. 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 5.0.0; sites on affected versions should update now. Disclosed October 2026, reported by Rasyid Abdi Gantoro.

Vulnerability Overview

The JS Help Desk – AI-Powered Support & Ticketing System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.0.0. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.

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 <= 4.0.0 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 5.0.0: builds <= 4.0.0 are affected, anything from 5.0.0 onward is not.

Remediation

Update to version 5.0.0, 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 5.0.0 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-103079https://www.wordfence.com/threat-intel/vulnerabilities/id/60c077fa-ac85-4761-838c-b1789b546103https://nvd.nist.gov/vuln/detail/CVE-2026-103079

Related records

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