CVE-2026-14928

JS Help Desk – AI-Powered Support & Ticketing System < 3.1.4 - Authenticated (Subscriber+) Information Exposure

Strategic Overview

Status
Patched in 3.1.4
Affected Version
< 3.1.4
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-14928
View all JS Help Desk – AI-Powered Support & Ticketing System vulnerabilities

At a glance

CVE-2026-14928 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor 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.4; sites on affected versions should update now. Disclosed August 2026, reported by Muni Nitish Kumar Yaddala.

Vulnerability Overview

The JS Help Desk – AI-Powered Support & Ticketing System plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to 3.1.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract sensitive user or configuration data.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in JS Help Desk < 3.1.4 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For JS Help Desk the fix is 3.1.4: builds < 3.1.4 are affected, anything from 3.1.4 onward is not.

Remediation

Update to version 3.1.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: JS Help Desk 3.1.4 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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