dbcve.org
Js Help DeskWordPress extension · Wiselyhub

CVE-2024-13606

HIGH · 7.5 CVSS v3.1 Published 2025-02-13
Fix available
A fix is available. Upgrade to 2.8.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The JS Help Desk WordPress plugin stores ticket attachments in an insecure publicly-accessible directory (/wp-content/uploads/jssupportticketdata). Unauthenticated attackers can directly access this directory to retrieve sensitive file attachments from support tickets without any authentication or access controls.

MitigationUpdate the plugin to version 2.8.9 or later if available. If no patch exists, restrict public access to the jssupportticketdata directory via .htaccess rules or move the uploads folder outside the web root.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Js Help DeskWordPress extension
Affected:< 2.8.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Wiselyhub Js Help Desk and note the version number displayed, or inspect the plugin header in /wp-content/plugins/js-help-desk/jshelpdesk.php
    Affected if version is below 2.8.9
  2. Verify the vulnerable directory exists
    Check if the directory /wp-content/uploads/jssupportticketdata/ exists on the server by listing the uploads folder or attempting to access it via web browser
    Affected if the directory exists and contains uploaded ticket attachments
  3. Test public accessibility of the attachment directory
    Attempt to directly access http://yourdomain.com/wp-content/uploads/jssupportticketdata/ in a browser without authentication - check if a file listing appears or if files can be downloaded
    Affected if the directory is publicly accessible with no authentication required
  4. Check for protective .htaccess rules
    Examine the .htaccess file in /wp-content/uploads/jssupportticketdata/ - look for rules that deny direct access or block directory listing
    Affected if no .htaccess file exists or the file does not contain deny rules, leaving the directory fully exposed

You are affected if the plugin version is below 2.8.9 AND the /wp-content/uploads/jssupportticketdata directory exists and is publicly accessible without authentication or access restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.8.9 or later
Fixed in 2.8.9
Interim mitigation

Update the plugin to version 2.8.9 or later if available. If no patch exists, restrict public access to the jssupportticketdata directory via .htaccess rules or move the uploads folder outside the web root.

Recommended fix High confidence

2.8.9

  1. Backup your WordPress site before making any changes
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate 'JS Help Desk' or 'JS Help Desk – The Ultimate Help Desk & Support Plugin'
  5. If an update is available, click 'Update Now' to upgrade to version 2.8.9
  6. Alternatively, download version 2.8.9 from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin
  7. Verify the plugin version shows 2.8.9 after updating
  8. Review /wp-content/uploads/jssupportticketdata directory permissions to ensure proper access controls are in place

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Js Help Desk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13606 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data