dbcve.org
Js Help DeskWordPress extension · Joomsky

CVE-2025-30880

HIGH · 7.5 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 2.9.3 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
Missing Authorization vulnerability in JoomSky JS Help Desk js-support-ticket allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JS Help Desk: from n/a through <= 2.9.2.

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

Missing authorization vulnerability in JoomSky JS Help Desk (js-support-ticket) allows unauthenticated or unauthorized users to access functionality they should not have access to due to incorrectly configured access control security levels. The issue affects versions up to and including 2.9.2.

MitigationUpdate to the latest version of JS Help Desk which includes proper authorization controls. If no update is available, review and enforce role-based access control (RBAC) permissions on all sensitive endpoints within the component.

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

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
None
Integrity
None
Availability
High

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

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 JoomSky JS Help Desk is installed
    Check for the js-support-ticket component directory in the Joomla installation, typically at /administrator/components/com_js-support-ticket or /components/com_js-support-ticket
    Affected if The component directory exists on the server
  2. Determine the installed version
    Locate the component's manifest XML file (typically manifest.xml, config.xml, or similar in the component directory) and read the version attribute, or access the Joomla administrator panel and view the component's version information under Extensions > Manage
    Affected if The installed version is 2.9.2 or lower (any version less than 2.9.3)
  3. Verify access control configuration
    Access the component's access control settings through the Joomla admin panel under Components > JS Help Desk > Configuration, or inspect the component's params in the #__extensions database table for permission-related settings
    Affected if Access control settings allow unauthenticated or low-privilege users to access sensitive administrative functions

If JS Help Desk is installed and the version is 2.9.2 or lower with permissive access control settings, the environment is affected by this authorization bypass vulnerability.

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.3 or later
Fixed in 2.9.3
Interim mitigation

Update to the latest version of JS Help Desk which includes proper authorization controls. If no update is available, review and enforce role-based access control (RBAC) permissions on all sensitive endpoints within the component.

Recommended fix Moderate confidence

2.9.3

  1. 1. Verify current JS Help Desk version by checking the Joomla extensions manager or the component's admin interface
  2. 2. Create a complete backup of the Joomla site including database and files
  3. 3. Download JS Help Desk version 2.9.3 from the official JoomSky source or Joomla extensions directory
  4. 4. Install the update through Joomla's extension manager (Extensions > Manage > Install)
  5. 5. Clear any Joomla and browser caches after update
  6. 6. Verify the new version is correctly installed (should show 2.9.3)
  7. 7. Test that admin functionality and front-end ticket submission work correctly

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

Fix this in Js Help Desk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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