dbcve.org
Js Help DeskWordPress extension · Wiselyhub

CVE-2022-46842

HIGH · 8.8 CVSS v3.1 Published 2023-02-02
Fix available
A fix is available. Upgrade to 2.7.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in JS Help Desk plugin <= 2.7.1 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the JS Help Desk WordPress plugin affecting versions 2.7.1 and below. The vulnerability allows an attacker to trick an authenticated user into performing unintended actions (such as modifying help desk settings or creating tickets) by forging a malicious request.

MitigationUpdate JS Help Desk plugin to the latest version when available. Until then, disable the plugin or implement anti-CSRF token validation on all state-changing actions within the plugin.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate the JS Help Desk plugin file
    Access your WordPress installation via file manager or FTP, navigate to /wp-content/plugins/ and look for a folder named 'js-help-desk', 'js-help-desk-wisely', or similar JS Help Desk related folder
    Affected if The plugin folder exists in the plugins directory
  2. Check the installed plugin version
    Open the main plugin PHP file (typically plugin-name.php) in the plugin folder and locate the 'Version' header in the plugin comment block, or check the version in WordPress admin under Plugins > Installed Plugins
    Affected if The reported version is 2.7.1 or below (any version less than 2.7.2)
  3. Verify plugin is active
    Log into WordPress admin dashboard, go to Plugins > Installed Plugins, and confirm the JS Help Desk plugin shows as 'Active'
    Affected if The plugin is active and the version is 2.7.1 or below
  4. Confirm plugin handles state-changing actions
    Review plugin functionality - CSRF affects actions that modify data such as changing help desk settings, creating tickets, or updating user profiles. Check if these features are accessible to authenticated users
    Affected if Authenticated users can access features that modify plugin settings or create/update tickets

Your environment is affected if the JS Help Desk plugin is installed, active, and running version 2.7.1 or below (any version prior to 2.7.2), as this version lacks proper CSRF token validation on state-changing actions.

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

Update JS Help Desk plugin to the latest version when available. Until then, disable the plugin or implement anti-CSRF token validation on all state-changing actions within the plugin.

Recommended fix High confidence

Js Help Desk version 2.7.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Js Help Desk' plugin
  4. Check if the current version is below 2.7.2
  5. If vulnerable, click 'Update Now' to upgrade to version 2.7.2
  6. Verify the update completed successfully by checking the plugin version displays 2.7.2 or higher

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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