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

CVE-2026-57652

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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
Unauthenticated Insecure Direct Object References (IDOR) in JS Help Desk <= 3.1.0 versions.

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

Unauthenticated IDOR vulnerability in JS Help Desk allows attackers to access or modify objects (such as tickets, user data, or internal records) without proper authorization, as the application fails to validate object-level access permissions on incoming requests.

MitigationUpgrade to a version beyond 3.1.0 that includes proper object-level authorization checks, or implement server-side validation that verifies the requesting user has permission to access the requested object.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 JS Help Desk installation
    Scan web servers for JS Help Desk application by checking for common paths such as /helpdesk, /support, /js-help-desk, or look for the application's login page or static assets containing 'js-help-desk' in the URL.
    Affected if JS Help Desk is found running on the server
  2. Determine installed version
    Check the application's version by visiting /changelog, /readme, or the admin dashboard footer. Alternatively, check version files in the web root directory if accessible, or inspect HTTP headers and HTML source for version strings.
    Affected if The installed version is 3.1.0 or lower, or the version cannot be determined but the application is publicly accessible
  3. Verify unauthenticated access is possible
    Attempt to access the main help desk interface, ticket submission forms, or user-facing pages without providing any authentication credentials. Check if the application allows viewing or interacting with the system without login.
    Affected if The application is accessible without authentication and accepts requests from unauthenticated users
  4. Test for IDOR on object references
    If the application exposes endpoints with numeric or predictable IDs (such as ticket.php?id=123, support/ticket/456, or api/tickets/789), attempt to access or modify these resources while unauthenticated to see if the application returns data or performs actions without authorization checks.
    Affected if The application returns sensitive data or allows modifications on unauthenticated requests using direct object references

The environment is affected if JS Help Desk version 3.1.0 or lower is installed and the application is accessible to unauthenticated users, particularly if direct object references (such as ticket or user IDs in URLs) can be accessed without authorization checks.

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

Upgrade to a version beyond 3.1.0 that includes proper object-level authorization checks, or implement server-side validation that verifies the requesting user has permission to access the requested object.

Recommended fix Moderate confidence

Latest version of JS Help Desk (version higher than 3.1.0)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins.
  3. 3. Locate JS Help Desk in the plugin list.
  4. 4. Check if an update is available. If so, update to the latest version of JS Help Desk.
  5. 5. Verify the update completed successfully.
  6. 6. Test that the help desk functionality works correctly after the update.
Caveat Unknown - review the plugin changelog for any breaking changes between your current version and the new version

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
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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