CVE-2026-14931

JS Help Desk <= 3.1.3 - Authenticated (Contributor+) User Email Disclosure

2026-07-13 00:00
Vaibhav Narkhede

Strategic Overview

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

At a glance

CVE-2026-14931 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the JS Help Desk WordPress plugin, affecting versions <= 3.1.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.1.4; sites on affected versions should update now. Disclosed July 2026, reported by Vaibhav Narkhede.

Vulnerability Overview

The JS Help Desk plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.1.3. This is due to missing capability check in the getuserlistajax function, allowing any authenticated user to retrieve user records including email addresses. This makes it possible for authenticated attackers, with contributor-level access and above, to obtain the email addresses of registered users by calling the user list AJAX endpoint without administrator or agent privileges.

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.3 takes an account at Contributor 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.3 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