CVE-2026-14929

JS Help Desk <= 3.1.3 - Missing Authorization to Authenticated (Subscriber+) Ticket Reply Modification

2026-07-13 00:00
Yaswanth Reddy Sunkara

Strategic Overview

Status
Patched in 3.1.4
Affected Plugin
JS Help Desk – AI-Powered Support & Ticketing System
Affected Version
<= 3.1.3
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2026-14929
View all JS Help Desk – AI-Powered Support & Ticketing System vulnerabilities

At a glance

CVE-2026-14929 is a medium-severity Incorrect Authorization 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 Subscriber level or above. The issue is fixed in version 3.1.4; sites on affected versions should update now. Disclosed July 2026, reported by Yaswanth Reddy Sunkara.

Vulnerability Overview

The JS Help Desk plugin for WordPress is vulnerable to unauthorized access in versions up to, and including, 3.1.3. This is due to missing authorization check in the editReply() function allowing any authenticated user to edit replies without verifying ownership or role. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify arbitrary ticket replies belonging to other users.

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-863: Incorrect Authorization

JS Help Desk <= 3.1.3 carries this weakness at editReply(), and reaching it takes an account at Subscriber level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. 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?

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.4 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-14929https://www.wordfence.com/threat-intel/vulnerabilities/id/c9b4b8cc-fa30-454d-b86a-55133f2ca993https://nvd.nist.gov/vuln/detail/CVE-2026-14929

Related records

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