dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-32535

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Authorization Bypass Through User-Controlled Key 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 <= 3.0.3.

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

Authorization bypass vulnerability in JoomSky JS Help Desk allows attackers to manipulate user-controlled keys (parameters) to access resources or functionality beyond their authorized permission level due to incorrectly configured access control security levels.

MitigationImplement proper server-side authorization checks that validate user permissions before allowing access to any resource, and ensure all user-controlled parameters are validated against the authenticated user's permissions.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm JoomSky JS Help Desk installation
    Identify if the JoomSky JS Help Desk component is installed on your Joomla environment by reviewing the extensions list in the Joomla administrator panel or checking for JS Help Desk related files in the /components directory.
    Affected if The product is installed and running.
  2. Identify installed version
    Locate the version information for JS Help Desk through the Joomla extensions manager, component admin page, or any version file included with the product.
    Affected if A version can be determined and falls within any affected release range.
  3. Review user-controlled parameter usage
    Examine application requests and parameters that reference user IDs, ticket IDs, or record identifiers. Check if these parameters can be modified in HTTP requests.
    Affected if The application uses predictable user-controlled parameters (such as user IDs, ticket IDs, or record IDs) in requests without proper validation.
  4. Test for unauthorized resource access
    Attempt to access resources belonging to other users by modifying parameter values in requests (e.g., change a ticket ID or user ID to one belonging to a different user account).
    Affected if Modifying parameter values allows access to resources or functionality that should require higher privileges.
  5. Verify access control enforcement
    Review application logs or perform manual testing to confirm whether the application validates user permissions server-side before returning sensitive data or granting access to functionality.
    Affected if The application relies solely on client-side parameters or fails to validate that the authenticated user has permission to access the requested resource.

You are affected if JoomSky JS Help Desk is installed and the application allows manipulation of user-controlled parameters to access resources beyond your authorized permission level.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper server-side authorization checks that validate user permissions before allowing access to any resource, and ensure all user-controlled parameters are validated against the authenticated user's permissions.

Recommended fix Moderate confidence

Latest available version (3.0.4 or later)

  1. Check the official JoomSky JS Help Desk plugin page or WordPress repository for the latest available version
  2. Upgrade JS Help Desk to the latest version available (version 3.0.4 or later if available)
  3. Verify the upgrade was successful and the plugin is functioning normally
  4. Review user access controls and permissions within the help desk system after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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