dbcve.org
Js Help DeskWordPress extension · Joomsky

CVE-2025-30882

HIGH · 7.5 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 2.9.2 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in JoomSky JS Help Desk js-support-ticket allows Path Traversal.This issue affects JS Help Desk: from n/a through <= 2.9.1.

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 · moderate confidence

A path traversal vulnerability in JoomSky's JS Help Desk (js-support-ticket) component allows attackers to escape restricted directories and access unauthorized files through manipulation of file path parameters. The vulnerability exists due to improper input validation on file path references in versions up to and including 2.9.1.

MitigationUpdate JS Help Desk to a version beyond 2.9.1 that implements proper path sanitization and input validation to block traversal sequences (../). If no update is available, implement web application firewall rules or input validation to reject path traversal patterns in file-related parameters.

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.9.2

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. Identify if JS Help Desk component is installed
    Check for the js-support-ticket component in your Joomla installation at /components/com_jshelpdesk/ or query your Joomla database for the component in the #__extensions table where element = 'jshelpdesk'
    Affected if The component directory or database entry exists on the system
  2. Determine the installed version of JS Help Desk
    Check the version file within the component directory (typically version.php or config.xml), or look in the Joomla #__extensions table manifest_cache field for the jshelpdesk entry
    Affected if The installed version is 2.9.1 or lower (< 2.9.2)
  3. Identify accessible file-related endpoints
    Review component files for functions handling file attachments, downloads, or file display features. Look for parameters that accept file paths (often named 'file', 'filename', 'path', or 'attachment'). Check if these endpoints are accessible without authentication.
    Affected if File-related parameters accepting user input are exposed and accessible to users

You are affected if the JS Help Desk component is installed with version 2.9.1 or lower and has accessible file-related functionality that accepts path parameters without validation.

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.9.2 or later
Fixed in 2.9.2
Interim mitigation

Update JS Help Desk to a version beyond 2.9.1 that implements proper path sanitization and input validation to block traversal sequences (../). If no update is available, implement web application firewall rules or input validation to reject path traversal patterns in file-related parameters.

Recommended fix Moderate confidence

JS Help Desk version 2.9.2

  1. 1. Backup your current JS Help Desk installation and database before making any changes.
  2. 2. Download JS Help Desk version 2.9.2 from the official JoomSky source or your trusted distribution channel.
  3. 3. Install the version 2.9.2 update following the standard JoomSky extension update procedure.
  4. 4. Verify the installation completed successfully by checking the admin panel for the correct version number.
  5. 5. Test that the Help Desk functionality works correctly after the update.

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30882 — 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-2025-30882 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