Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege WordPress user
-
ExploitEnumerate ticket object references
-
ExecutionBypass improper access-control check
-
ImpactRead other users' ticket data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires a valid authenticated low-privileged account on the WordPress site (PR:L) - for example, any registered user able to interact with the JS Help Desk ticketing feature. Exploitation hinges on the plugin's incorrectly configured access-control level for ticket objects: the attacker substitutes or enumerates a user-controlled key (object reference) to reach tickets they do not own. Limiting factors: authentication is mandatory (not exploitable by fully anonymous users), impact is confined to confidentiality (reading data; no write or availability impact), and only installations running JS Help Desk versions up to and including 4.0.0 are affected. |
| Impact | This is a moderate-severity, low-priority issue rather than an urgent one. The CVSS 3.1 base score is 4.3 (Medium), driven by a network vector with low complexity but requiring low-privilege authentication (AV:N/AC:L/PR:L/UI:N) and yielding only limited confidentiality impact (C:L/I:N/A:N) - consistent with an IDOR (CWE-639) that exposes other users' support-ticket data but allows no modification or disruption. No EPSS score, SSVC decision, KEV listing, or POC was provided in the input: there is no public exploit identified at time of analysis and no evidence of active exploitation. The signals are internally consistent - the description (authorization bypass via user-controlled key) aligns with the CVSS vector's PR:L and C:L/I:N/A:N profile - so there is no conflict to flag. The main caveat is that the exact object/data exposed is not detailed beyond 'support ticket' context, so real-world sensitivity depends on what ticket contents contain (potentially PII or internal correspondence). |
| Exploit ScenarioDerived | An attacker registers or already holds a low-privileged WordPress account on a site running JS Help Desk (≤ 4.0.0), then manipulates a user-controlled identifier (such as a ticket ID) in a request to retrieve support tickets belonging to other users. No public exploit code was identified, but IDOR flaws of this kind are typically trivial to exploit by incrementing or substituting object references once an authenticated session exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Authenticated low-privileged users can read support tickets belonging to other users in the Ahmad JS Help Desk WordPress plugin through version 4.0.0 by manipulating user-controlled object references. This is a classic insecure direct object reference (IDOR, CWE-639) limited to confidentiality impact; authentication is required per the CVSS vector (PR:L), and no public exploit code has been identified at time of analysis. With a CVSS score of 4.3 and no active exploitation reported, this is a moderate-severity, low-priority issue.
RemediationAI
No vendor-released patch was identified at time of analysis based on the available data. Until an official fix is published, site administrators should consider disabling the JS Help Desk plugin if ticketing functionality is not essential, which removes the attack surface but may disrupt support workflows. Where the plugin must remain active, restrict user registration and audit roles so that only trusted users can interact with the help desk; this reduces the pool of authenticated accounts that could exploit the IDOR but does not eliminate the underlying flaw. Additional compensating controls include monitoring web server and plugin access logs for unusual ticket ID enumeration patterns and applying virtual patching or WAF rules to block sequential or unauthorized ticket access attempts, though such rules require tuning to avoid false positives. Consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/js-support-ticket/vulnerability/wordpress-js-help-desk-plugin-4-0-0-insecure-direct-object-references-idor-vulnerability?_s_id=cve for updated patch information as it becomes available.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability class is CWE-639 (Authorization Bypass Through User-Controlled Key), commonly known as IDOR. In the JS Help Desk WordPress plugin, the application uses a user-supplied identifier, such as a ticket ID or object reference, to retrieve ticket records without verifying that the requesting user owns or is authorized to view that specific ticket. Because the plugin relies on incorrectly configured access-control levels for ticket objects, any authenticated low-privileged account that can interact with the ticketing feature may substitute or enumerate keys to access other users' tickets. The CPE entry cpe:2.3:a:ahmad:js_help_desk:*:*:*:*:*:*:*:* identifies the affected product as the JS Help Desk plugin maintained by Ahmad, with all versions up to and including 4.0.0 in scope. The CVSS vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N confirms the attack is network-reachable, requires low privileges, needs no user interaction, and is confined to low confidentiality impact with no integrity or availability effect.
Know when Js Help Desk gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Remotely reachable IDOR requiring a low-privilege authenticated account (PR:L), no user interaction, exposing other users' ticket data (C:L) with no integrity or availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Authorization Bypass Through User-Controlled Key vulnerability in Ahmad JS Help Desk js-support-ticket allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JS Help Desk: from n/a through 4.0.0.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Js Help Desk
View allImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in JS Help Desk JS He
Unauthenticated file upload and arbitrary ticket attachment in JS Help Desk WordPress plugin (all versions before 3.1.4)
User email enumeration in the JS Help Desk WordPress plugin (versions before 3.1.4) allows any Contributor-level site us
JS Help Desk WordPress plugin before 3.1.4 exposes all support ticket content to any authenticated WordPress user due to
Insecure Direct Object Reference (IDOR) in JS Help Desk WordPress plugin before 3.1.5 exposes support ticket data to any
Unrestricted file upload in JS Help Desk WordPress plugin. CVSS 10.0.
Missing Authorization vulnerability in JS Help Desk JS Help Desk - Best Help Desk & Support Plugin allows Accessing Func
Missing Authorization vulnerability in JS Help Desk JS Help Desk - Best Help Desk & Support Plugin.8.3. Rated critical s
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in JoomSky JS Help De
SQL injection in the JS Help Desk WordPress plugin versions 3.0.9 and earlier allows remote unauthenticated attackers to
Missing Authorization vulnerability in JoomSky JS Help Desk js-support-ticket allows Exploiting Incorrectly Configured A
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in JoomSky JS Help Desk all
EUVD-2026-92308
GHSA-6f4g-xj5p-3c9x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB