dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2023-7337

HIGH · 7.5 CVSS v3.1 Published 2026-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The JS Help Desk – AI-Powered Support & Ticketing System plugin for WordPress is vulnerable to SQL Injection via the 'js-support-ticket-token-tkstatus' cookie in version 2.8.2 due to an incomplete fix for CVE-2023-50839 where a second sink was left with insufficient escaping on the user supplied values and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 · high confidence

The JS Help Desk WordPress plugin version 2.8.2 contains a SQL injection vulnerability in the 'js-support-ticket-token-tkstatus' cookie parameter. This is an incomplete fix for CVE-2023-50839 where a second code path was left with insufficient input escaping and no prepared statements, allowing unauthenticated attackers to inject arbitrary SQL queries via the cookie value.

MitigationUpdate to the latest version of the plugin when released. If no patch is available, disable the plugin or implement a WAF rule to block SQL injection attempts targeting the js-support-ticket-token-tkstatus cookie.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

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 installation
    Check the /wp-content/plugins/ directory for a folder named 'js-support-ticket' or 'js-help-desk', or view the installed plugins list in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder or listing is found in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically js-support-ticket.php) and locate the 'Version' header comment in the plugin file, or check the version column in WordPress admin Plugins page
    Affected if The version listed is 2.8.2 or any version prior to the complete CVE-2023-50839 patch
  3. Verify the plugin is active
    Check the WordPress admin Plugins page to confirm the JS Help Desk plugin is currently activated, or query the wp_options table for option_name='active_plugins' containing the plugin slug
    Affected if The plugin shows as active in the admin or active_plugins option contains the plugin reference
  4. Confirm cookie processing capability exists
    Inspect the plugin files for the token-tkstatus cookie handling code, typically in files related to ticket status or token validation, looking for $_COOKIE['js-support-ticket-token-tkstatus'] usage
    Affected if The vulnerable cookie parameter processing code exists in the active plugin files

If the JS Help Desk plugin is installed at version 2.8.2 or before the complete CVE-2023-50839 fix, is active, and contains the js-support-ticket-token-tkstatus cookie handling code, the environment is vulnerable to SQL injection via that parameter.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin when released. If no patch is available, disable the plugin or implement a WAF rule to block SQL injection attempts targeting the js-support-ticket-token-tkstatus cookie.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version higher than 2.8.2)

  1. 1. Check the current version of the JS Help Desk plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. If the installed version is 2.8.2, update to the latest available version from the WordPress plugin repository
  4. 4. Alternatively, go to Plugins > Add New > Upload and upload the latest patched version of the plugin
  5. 5. Verify the update was successful and test the ticketing system functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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