dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-2511

HIGH · 7.5 CVSS v3.1 Published 2026-03-26
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 `multiformid` parameter in the `storeTickets()` function in all versions up to, and including, 3.0.4. This is due to the user-supplied `multiformid` value being passed to `esc_sql()` without enclosing the result in quotes in the SQL query, rendering the escaping ineffective against payloads that do not contain quote characters. 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 fails to properly secure the `multiformid` parameter in the `storeTickets()` function. Although `esc_sql()` is used, the lack of quote enclosure around the parameter in the SQL query allows attackers to inject SQL without quote characters, bypassing the escaping entirely. This unauthenticated SQL injection can be exploited to extract sensitive data from the database.

MitigationUpdate the plugin to a version beyond 3.0.4 when a patched release becomes available. Until then, consider disabling the affected form submission functionality or implementing a web application firewall (WAF) rule to block SQL injection attempts targeting the `multiformid` parameter.

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. Verify JS Help Desk plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'JS Help Desk' or check the filesystem at /wp-content/plugins/js-help-desk/ for the plugin directory
    Affected if The plugin is installed and active
  2. Check installed plugin version
    In WordPress admin Plugins page, find JS Help Desk and note the version number displayed; alternatively, read the main plugin file header in /wp-content/plugins/js-help-desk/
    Affected if Version is 3.0.4 or lower (the vulnerable version range)
  3. Confirm ticket submission feature is enabled
    Navigate to WordPress admin > JS Help Desk settings and verify that ticket submission/form functionality is active and not disabled
    Affected if The storeTickets() function is accessible via enabled form submissions
  4. Identify the vulnerable endpoint exposure
    Check if the ticket submission form (typically at /?jshd=1 or similar endpoint handling storeTickets) is publicly accessible without authentication
    Affected if The endpoint accepts unauthenticated POST requests with the multiformid parameter

If the JS Help Desk plugin versions 3.0.4 or below is installed with ticket submission enabled and publicly accessible, the environment is affected by this unauthenticated SQL injection vulnerability.

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 the plugin to a version beyond 3.0.4 when a patched release becomes available. Until then, consider disabling the affected form submission functionality or implementing a web application firewall (WAF) rule to block SQL injection attempts targeting the `multiformid` parameter.

Recommended fix Moderate confidence

Latest version available in the WordPress plugin repository (check plugins.trac.wordpress.org for version history)

  1. 1. Check the WordPress plugin repository for the JS Help Desk – AI-Powered Support & Ticketing System plugin
  2. 2. Verify the latest available version of the plugin
  3. 3. Update the plugin to the latest version available in the WordPress plugin repository
  4. 4. Confirm the update was successful and the new version is running

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

Have this fixed 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 help mitigating

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-2026-2511 — 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-2026-2511 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