dbcve.org
Js Help DeskWordPress extension · Wiselyhub

CVE-2022-46839

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-05
Fix available
A fix is available. Upgrade to after 2.7.1 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
Unrestricted Upload of File with Dangerous Type vulnerability in JS Help Desk JS Help Desk – Best Help Desk & Support Plugin.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

The JS Help Desk WordPress plugin versions through 2.7.1 contains an unrestricted file upload vulnerability allowing attackers to upload dangerous file types (e.g., executable PHP scripts) without proper validation. This could enable remote code execution and complete server compromise.

MitigationUpdate to the latest patched version of JS Help Desk plugin when released. Until then, disable the file upload functionality or implement web application firewall rules to block executable file uploads.

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

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. Identify if JS Help Desk plugin is installed
    Check WordPress plugins directory or wp-content/plugins folder for 'js-help-desk' or 'wiselyhub-js-help-desk' folder
    Affected if The plugin folder exists in the WordPress installation
  2. Check installed plugin version
    Read the main plugin PHP file header (e.g., js-help-desk.php) or check in WordPress admin under Plugins > Installed Plugins
    Affected if Version is 2.7.1 or lower, or version cannot be determined (indicating outdated installation)
  3. Verify file upload functionality is accessible
    Check plugin settings page at /wp-admin/admin.php?page=js-help-desk-settings or inspect if upload endpoint exists (e.g., /?action=js_help_upload)
    Affected if File upload feature is enabled and accessible to unauthenticated or low-privilege users
  4. Inspect upload directory for suspicious files
    Check wp-content/uploads/js-help-desk or similar upload folders for .php, .phtml, or other executable file extensions
    Affected if Unexpected script files (.php, .exe, .sh) are present in the upload directory

A user is affected if the JS Help Desk plugin version is 2.7.1 or lower and the file upload feature is enabled, allowing potential remote code execution through malicious file uploads.

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 a release after 2.7.1
Interim mitigation

Update to the latest patched version of JS Help Desk plugin when released. Until then, disable the file upload functionality or implement web application firewall rules to block executable file uploads.

Recommended fix High confidence

Upgrade to JS Help Desk version 2.7.2 or later

  1. 1. Back up your WordPress site database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate the 'JS Help Desk' plugin.
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version.
  6. 6. If no automatic update is available, download the latest version from the WordPress plugin repository and manually upload it via Plugins > Add New > Upload Plugin.
  7. 7. Verify the plugin is running version 2.7.2 or higher after updating.
  8. 8. Test the help desk functionality to ensure the update did not break existing features.
Caveat Review the plugin changelog for any feature changes between 2.7.1 and the new version before upgrading in production environments

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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