dbcve.org
Js Help DeskWordPress extension · Wiselyhub

CVE-2023-50839

CRITICAL · 9.8 CVSS v3.1 Published 2023-12-28
Fix available
A fix is available. Upgrade to after 2.8.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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') 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.8.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

SQL Injection vulnerability in JS Help Desk WordPress plugin allows attackers to inject malicious SQL commands via unsanitized user input. The critical severity (CVSS 9.8) suggests unauthenticated exploitation is possible.

MitigationUpgrade to latest version of JS Help Desk plugin; until then, disable the plugin or implement WAF rules to block SQL injection attempts.

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.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. Confirm JS Help Desk plugin installation
    Locate the plugin directory at wp-content/plugins/ and look for a folder named js-help-desk or wiselyhub-js-help-desk, or check the WordPress admin Plugins page for an entry named Wiselyhub Js Help Desk or JS Help Desk
    Affected if The plugin is installed in the WordPress plugins directory
  2. Identify installed plugin version
    Open the main plugin PHP file (typically js-help-desk.php) in the plugin folder and read the Version field from the plugin header comment, or inspect the readme.txt file for the Stable tag version number
    Affected if Version is 2.8.1 or any version below it (e.g., 2.8.0, 2.7.5, etc.)
  3. Verify plugin is active
    Access WordPress admin panel at /wp-admin/plugins.php and check if the plugin status shows as Active, or query the wp_options table for the active_plugins option to confirm the plugin is enabled
    Affected if Plugin is active and accessible to unauthenticated users

The environment is affected if the Wiselyhub JS Help Desk plugin is installed, active, and running version 2.8.1 or lower, allowing unauthenticated attackers to inject SQL commands through unsanitized input fields.

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.8.1
Interim mitigation

Upgrade to latest version of JS Help Desk plugin; until then, disable the plugin or implement WAF rules to block SQL injection attempts.

Recommended fix Moderate confidence

Update to version 2.8.2 or later (verify latest version from vendor)

  1. Check the WordPress admin panel for the JS Help Desk plugin and note the current installed version
  2. Visit the official WordPress plugin repository or contact the vendor to verify if a newer version exists beyond 2.8.1
  3. If a newer version (2.8.2 or later) is available, update the plugin through the WordPress admin or via FTP
  4. After updating, verify the plugin version in the installed plugins list
  5. Test the help desk functionality to ensure the update did not break existing features
  6. Review patchstack.com or the vendor's security advisory for any specific migration or configuration steps required after the update
Caveat Unknown - check vendor release notes for any breaking changes in the new version

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

Fix this in Js Help Desk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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