LiveActive security incident?Get immediate response
CVE Record

CVE-2024-13606: JS Help Desk – The Ultimate Help Desk & Support Plugin <= 2.8.8 - Unauthenticated Sensitive Information Exposure Through Unprotected Directory

The JS Help Desk – The Ultimate Help Desk & Support Plugin plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.8.8 via the 'jssupportticketdata' directory. This makes it possible for unauthenticated attackers to extract sensitive data stored insecurely in the /wp-content/uploads/jssupportticketdata directory which can contain file attachments included in support tickets.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-13606 affects the JS Help Desk WordPress support plugin up to and including version 2.8.8. Ticket attachments may be stored in an unprotected uploads directory, allowing unauthenticated outsiders to access sensitive files if the site is exposed.

Executive priority

Treat this as a high-priority confidentiality issue for any customer-facing WordPress support site. Urgency depends on whether ticket attachments contain regulated, contractual, customer, or security-sensitive information.

Technical view

The issue is CWE-200 sensitive information exposure through the plugin’s jssupportticketdata upload directory under wp-content/uploads. The CVSS 3.1 score is 7.5 because exploitation is network-accessible, low-complexity, unauthenticated, and impacts confidentiality only.

Likely exposure

Exposure is most likely on public WordPress sites using JS Help Desk through version 2.8.8, especially where support tickets include customer, employee, legal, billing, or security attachments.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is still practical because the described condition is unauthenticated access to files in a predictable public uploads location.

Researcher notes

Evidence supports an unauthenticated sensitive information exposure in JS Help Desk through 2.8.8. The provided sources do not name a fixed version, confirm exploitation, or define exact remediation steps beyond the vulnerable storage condition.

Mitigation direction

  • Inventory WordPress sites for JS Help Desk plugin versions up to 2.8.8.
  • Check vendor or WordPress plugin guidance for a fixed version or official mitigation.
  • Review exposed ticket attachments for sensitive data handling and retention decisions.
  • Restrict public access to ticket attachment storage using approved server controls.
  • Consider disabling the plugin if sensitive attachments remain exposed and no fix is available.

Validation and detection

  • Confirm whether the plugin is installed and identify its exact version.
  • Determine whether support ticket attachments are stored in jssupportticketdata.
  • Assess external reachability of that directory through approved defensive testing.
  • Review web logs for unauthenticated requests to the affected uploads path.
  • Document affected files and impacted data owners before cleanup.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-13606 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-13606Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
rabilalJS Help Desk – AI-Powered Support & Ticketing System0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.