dbcve.org
Js Help DeskWordPress extension · Joomsky

CVE-2022-47151

HIGH · 8.6 CVSS v3.1 Published 2024-04-17
Fix available
A fix is available. Upgrade to 2.7.2 or later.
See remediation →
95/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.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

SQL Injection vulnerability in the JS Help Desk WordPress plugin allows attackers to inject malicious SQL commands through unsanitized input. With a CVSS of 8.6, this could enable unauthorized data access, modification, or deletion from the database.

MitigationApply available patches or upgrade to the latest version of the plugin. If no patch exists, implement parameterized queries (prepared statements) for all database interactions using user-supplied input, following OWASP SQL Injection prevention guidelines.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

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. Check if Joomsky Js Help Desk plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Joomsky JS Help Desk' or 'JS Help Desk' in the list of installed plugins.
    Affected if Plugin is listed in the installed plugins page
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin to view its details, or check the plugin's main PHP file header for the 'Version' comment. The file is typically located at /wp-content/plugins/js-help-desk/ or similar.
    Affected if Version number is lower than 2.7.2 or no version is displayed
  3. Verify the plugin is active
    In WordPress admin > Plugins, check if the Joomsky JS Help Desk plugin shows 'Active' status under the 'Status' column.
    Affected if Plugin is active and version is below 2.7.2
  4. Check plugin accessibility
    Attempt to access the help desk frontend or admin interface. The plugin typically exposes endpoints like /?jshd=1 or /wp-admin/admin.php?page=jshd or frontend ticket submission forms.
    Affected if Plugin is accessible (active) and version is below 2.7.2, making the SQL injection vulnerability potentially exploitable

A user is affected if the Joomsky JS Help Desk plugin is installed, active, and running at a version lower than 2.7.2.

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

Apply available patches or upgrade to the latest version of the plugin. If no patch exists, implement parameterized queries (prepared statements) for all database interactions using user-supplied input, following OWASP SQL Injection prevention guidelines.

Recommended fix High confidence

2.7.2 or later

  1. 1. Back up your WordPress database and files before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find 'JS Help Desk – Best Help Desk & Support Plugin' in the installed plugins list
  4. 4. Click 'Update now' if an update is available, or manually upload version 2.7.2 or later from the WordPress plugin repository
  5. 5. Verify the plugin version after update by checking the installed plugins list
  6. 6. 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
  • 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-47151 — 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-47151 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