dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-40762

HIGH · 7.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 →
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
Unauthenticated SQL Injection in WPGraphQL < 2.11.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 · high confidence

Unauthenticated SQL Injection vulnerability in WPGraphQL plugin for WordPress affecting versions prior to 2.11.1. Attackers can exploit this without authentication to inject malicious SQL queries, potentially allowing data exfiltration, manipulation, or complete database compromise.

MitigationUpdate WPGraphQL to version 2.11.1 or later. If immediate patching is not feasible, implement a Web Application Firewall (WAF) with SQL injection rules as a compensating control.

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Verify WPGraphQL plugin is installed
    Navigate to WordPress admin > Plugins or inspect the wp-content/plugins/ directory for the wp-graphql folder
    Affected if WPGraphQL plugin is not present on the system
  2. Confirm WPGraphQL is active
    Check WordPress admin > Plugins for WPGraphQL status, or query the /wp-json/graphql endpoint with a basic introspection query
    Affected if Plugin is installed but inactive (vulnerability not reachable)
  3. Identify installed WPGraphQL version
    Inspect the main plugin file (wp-graphql/wp-graphql.php) header for 'Version:' comment, or check the Plugins page in WordPress admin
    Affected if Version number is present and below 2.11.1
  4. Verify GraphQL endpoint is publicly accessible
    Attempt a GET request to /graphql or /wp-json/graphql without authentication
    Affected if Endpoint returns a valid GraphQL response without requiring auth
  5. Confirm vulnerability applicability
    If version is below 2.11.1 and GraphQL endpoint is accessible without authentication, compare against the affected version range
    Affected if Installed version is prior to 2.11.1 AND the GraphQL endpoint accepts unauthenticated requests

The environment is affected if WPGraphQL plugin is active, the GraphQL endpoint is accessible without authentication, and the installed version is below 2.11.1.

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 WPGraphQL to version 2.11.1 or later. If immediate patching is not feasible, implement a Web Application Firewall (WAF) with SQL injection rules as a compensating control.

Recommended fix High confidence

WPGraphQL version 2.11.1 or later

  1. Backup your WordPress database and files before making any changes
  2. Navigate to WordPress Admin > Plugins > WPGraphQL
  3. If an update is available, click 'Update Now' to upgrade to version 2.11.1 or later
  4. Alternatively, update via WP-CLI: `wp plugin update wp-graphql`
  5. After updating, verify the installed version is 2.11.1 or higher in Plugins > Installed Plugins
  6. Review the plugin changelog for any noted changes that may affect your site
Caveat Check the plugin changelog before upgrading; minor version updates typically have minimal breaking changes but custom GraphQL schemas may need testing

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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