dbcve.org
Js Help DeskWordPress extension · Joomsky

CVE-2025-30886

CRITICAL · 10.0 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 2.9.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in JoomSky JS Help Desk js-support-ticket allows SQL Injection.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 · high confidence

SQL injection vulnerability in JoomSky JS Help Desk (js-support-ticket) component for Joomla allows unauthenticated attackers to inject malicious SQL commands via unsanitized user input in the ticket system, potentially leading to complete database compromise.

MitigationApply vendor patch or upgrade to JS Help Desk version > 2.9.2; if no patch available, implement parameterized queries/prepared statements for all database operations and add input validation at application layer.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 JS Help Desk version installed
    Locate the js-support-ticket component in the Joomla administrator extensions manager and note the installed version number
    Affected if The installed version is lower than 2.9.3 (e.g., 2.9.2, 2.9.1, 2.9.0, or earlier)
  2. Confirm component is active
    In Joomla admin, navigate to Components > JS Help Desk and verify the component is published and accessible
    Affected if The js-support-ticket component is installed and enabled
  3. Verify ticket submission functionality is accessible
    Attempt to access the front-end ticket submission page (typically at /index.php?option=com_jssupportticket or similar) without authentication
    Affected if The ticket submission form is publicly accessible without requiring authentication
  4. Check for recent database anomalies
    Review database logs for unexpected or suspicious SQL queries, particularly in tables related to tickets (e.g., #__js_ticket_* tables) that may indicate exploitation
    Affected if Unusual SQL patterns or injection attempts appear in database query logs

You are affected if JS Help Desk version is below 2.9.3 AND the ticket system component is active and accessible to unauthenticated users.

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

Apply vendor patch or upgrade to JS Help Desk version > 2.9.2; if no patch available, implement parameterized queries/prepared statements for all database operations and add input validation at application layer.

Recommended fix High confidence

2.9.3

  1. Log in to the WordPress admin dashboard where js-support-ticket is installed
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'JS Help Desk' or 'js-support-ticket' in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 2.9.3
  5. Alternatively, download version 2.9.3 from the official JoomSky website or WordPress plugin repository, then upload and replace the existing installation
  6. After upgrading, verify the plugin version shows 2.9.3 or higher

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
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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