dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-48964

HIGH · 8.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Subscriber SQL Injection in ELEX WordPress HelpDesk & Customer Ticketing System <= 3.3.6 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 · high confidence

SQL injection vulnerability in the ELEX WordPress HelpDesk & Customer Ticketing System plugin allows authenticated subscribers to inject malicious SQL queries through unsanitized input, potentially enabling unauthorized data access or manipulation of the database.

MitigationUpgrade to version 3.3.7 or later which patches the SQL injection vulnerability. Until then, disable the plugin or restrict subscriber-level access if possible.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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. Confirm plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ELEX WordPress HelpDesk & Customer Ticketing System' or search for 'helpdesk' in the plugins list
    Affected if Plugin is present in the WordPress installation
  2. Check installed plugin version
    Click on the plugin name in the Plugins list to view its details, or check the plugin files in wp-content/plugins/elex-wordpress-helpdesk for a version file or readme.txt
    Affected if Version is below 3.3.7 or version cannot be determined (treat as vulnerable)
  3. Verify subscriber-level access exists
    In WordPress admin, go to Users > All Users and check for any users with the 'Subscriber' role; also go to Settings > General to confirm 'Anyone can register' is enabled with Subscriber as default role
    Affected if Subscriber role users exist and can register, making the vulnerable input path accessible
  4. Test if ticketing feature accepts subscriber input
    Log in as a subscriber user and attempt to access the helpdesk ticket submission form at the plugin's frontend endpoint (typically /helpdesk/ or /support/ or check plugin settings for ticket submission URL)
    Affected if Subscriber role can submit tickets through the plugin's frontend interface

User is affected if the ELEX HelpDesk plugin is installed with a version below 3.3.7 and subscriber-level users can access the ticket submission functionality.

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

Upgrade to version 3.3.7 or later which patches the SQL injection vulnerability. Until then, disable the plugin or restrict subscriber-level access if possible.

Recommended fix Moderate confidence

Version 3.3.7 or later

  1. Check the current version of ELEX WordPress HelpDesk & Customer Ticketing System plugin installed on your WordPress site
  2. Review the plugin's changelog or release notes on the WordPress plugin repository for version 3.3.7 or higher
  3. Update the plugin to the latest available version (3.3.7 or later) via WordPress admin dashboard > Plugins > Updates, or via FTP/SSH if automatic updates are disabled
  4. After updating, verify the fix by testing core ticket creation and retrieval functionality as a subscriber-level user
  5. Ensure the WordPress installation, including all other plugins and themes, is kept up to date
Caveat Review plugin settings and customizations after upgrade as minor compatibility changes may occur

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