dbcve.org
Js Help DeskWordPress extension · Joomsky

CVE-2022-46838

CRITICAL · 9.1 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 2.7.2 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 Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JS Help Desk – Best Help Desk & Support Plugin: from n/a through 2.7.1.

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

This is a Missing Authorization (Broken Access Control) vulnerability in the JS Help Desk WordPress plugin. The CVSS 9.1 score indicates the flaw allows unauthenticated or unauthorized attackers to access functionality or data they should not be permitted to reach, likely due to missing capability checks or improper access control validation on certain plugin functions or endpoints.

MitigationImplement proper authorization checks (e.g., current_user_can() capability verification) on all sensitive plugin functions and admin actions; verify access control configuration aligns with WordPress security levels; upgrade to patched version if 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.7.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 if Joomsky Js Help Desk plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'js-help-desk', 'jshelpdesk', or similar variants containing 'js help desk' or 'joomsky'. Alternatively, list installed plugins via WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder exists in the WordPress plugins directory or the plugin appears in the WordPress admin plugin list.
  2. Determine the installed plugin version
    If the plugin folder is found, open the main plugin PHP file (often named plugin-name.php or includes a version comment header) and locate the 'Version' field in the plugin header comment block. Alternatively, check the plugin row in WordPress admin plugins list which displays the version.
    Affected if The version number displayed is lower than 2.7.2 (e.g., 2.7.1, 2.7.0, 2.6.x, etc.) or no version is listed but the plugin is present.
  3. Verify the plugin is active on the site
    In WordPress admin, go to Plugins > Installed Plugins and check if Joomsky Js Help Desk shows as 'Active' (not 'Inactive' or 'Must Use'). For headless checks, query the WordPress options table for the active_plugins option or check site configuration.
    Affected if The plugin is installed AND active on the WordPress site.

A user is affected if the Joomsky Js Help Desk plugin is installed, active, and running a version lower than 2.7.2, as the missing authorization vulnerability could allow unauthorized access to sensitive functionality or data.

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.7.2 or later
Fixed in 2.7.2
Interim mitigation

Implement proper authorization checks (e.g., current_user_can() capability verification) on all sensitive plugin functions and admin actions; verify access control configuration aligns with WordPress security levels; upgrade to patched version if available.

Recommended fix High confidence

2.7.2

  1. Upgrade the JS Help Desk plugin to version 2.7.2 or later

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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