dbcve.org
Js Help DeskWordPress extension · Joomsky

CVE-2024-43274

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 2.8.7 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
Missing Authorization vulnerability in JS Help Desk JS Help Desk – Best Help Desk & Support Plugin allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects JS Help Desk – Best Help Desk & Support Plugin: from n/a through 2.8.6.

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 the JS Help Desk WordPress plugin allows unauthenticated or unauthorized users to access sensitive help desk functionality that should be restricted by access control lists (ACLs). With CVSS 9.8, this is a critical severity issue requiring no privileges or user interaction to exploit, likely allowing complete bypass of authentication gates on certain plugin functions.

MitigationUpdate the JS Help Desk plugin to the latest patched version (beyond 2.8.6) as soon as a fix is released. If no patch is available, consider disabling the plugin or implementing a Web Application Firewall rule to mitigate unauthorized access until a fix is available.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Verify JS Help Desk plugin is installed
    Check WordPress admin under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named js-help-desk, jshelpdesk, or similar variant containing 'Joomsky'
    Affected if The Joomsky Js Help Desk plugin is present in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate the version number displayed for the Joomsky Js Help Desk entry, or read the Version header from the main plugin PHP file in the plugin directory
    Affected if Installed version is lower than 2.8.7 (e.g., 2.8.6, 2.8.5, etc.)
  3. Test unauthenticated access to plugin functions
    Send HTTP requests to common plugin AJAX endpoints (typically /wp-admin/admin-ajax.php?action=jshd_*) or direct access URLs without providing valid authentication cookies or credentials
    Affected if The plugin returns expected data or executes actions without requiring valid authentication (401/403 not returned)
  4. Review access control on sensitive REST endpoints
    If the plugin exposes REST API routes, enumerate them and attempt to call protected endpoints (such as those handling tickets, users, or settings) without an API key or session
    Affected if Sensitive REST endpoints respond successfully to unauthenticated requests

Your environment is affected if the Joomsky Js Help Desk plugin is installed with a version below 2.8.7 and sensitive plugin functions are accessible without valid authentication credentials.

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.8.7 or later
Fixed in 2.8.7
Interim mitigation

Update the JS Help Desk plugin to the latest patched version (beyond 2.8.6) as soon as a fix is released. If no patch is available, consider disabling the plugin or implementing a Web Application Firewall rule to mitigate unauthorized access until a fix is available.

Recommended fix High confidence

2.8.7

  1. Backup your WordPress site and database before making any changes
  2. Navigate to your WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find 'JS Help Desk' or 'JS Help Desk – Best Help Desk & Support Plugin'
  5. Check the current version is below 2.8.7
  6. Click 'Update Now' if an update is available, or manually download version 2.8.7 from the WordPress plugin repository
  7. After updating, verify the new version is 2.8.7 or higher
  8. Test that the help desk functionality works correctly

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

Fix this in Js Help Desk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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