dbcve.org
WpgraphqlWordPress extension · Wpengine

CVE-2023-23684

MEDIUM · 6.5 CVSS v3.1 Published 2023-11-13
Fix available
A fix is available. Upgrade to after 1.14.5 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Server-Side Request Forgery (SSRF) vulnerability in WPGraphQL.This issue affects WPGraphQL: from n/a through 1.14.5.

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

Server-Side Request Forgery (SSRF) vulnerability in WPGraphQL plugin for WordPress. Attackers could potentially make the server perform unauthorized requests to internal or external resources through the GraphQL API. The vulnerability exists in versions up to and including 1.14.5.

MitigationUpdate WPGraphQL to the latest version (1.14.6 or later) which contains the patch for this SSRF vulnerability. If immediate update is not possible, restrict access to the GraphQL endpoint via authentication or network-level controls.

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
WpgraphqlWordPress extension
Affected:<= 1.14.5

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

CVSS:3.1/AV:N/AC:L/PR:L/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 WPGraphQL is installed
    Check the WordPress plugins directory or view installed plugins in wp-admin to confirm WPGraphQL is present and active
    Affected if WPGraphQL plugin is installed and active on the site
  2. Check installed version
    View the WPGraphQL plugin details in WordPress admin (Plugins > Installed Plugins > WPGraphQL) or inspect the plugin header in the main plugin file to find the version number
    Affected if Version is 1.14.5 or lower (any version up to and including 1.14.5)
  3. Confirm GraphQL endpoint is exposed
    Access the GraphQL endpoint (typically at /graphql or /wp-json/graphql/v1) without authentication to verify it is publicly accessible
    Affected if The endpoint returns a valid GraphQL schema or response without requiring authentication
  4. Check endpoint access controls
    Inspect WordPress permissions settings or any authentication plugins to determine if unauthenticated requests to the GraphQL endpoint are allowed
    Affected if Unauthenticated access to the GraphQL endpoint is permitted and the plugin version is 1.14.5 or lower

You are affected if the WPGraphQL plugin version is 1.14.5 or lower AND the GraphQL endpoint is accessible without authentication, allowing potential SSRF attacks through the API.

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 a release after 1.14.5
Interim mitigation

Update WPGraphQL to the latest version (1.14.6 or later) which contains the patch for this SSRF vulnerability. If immediate update is not possible, restrict access to the GraphQL endpoint via authentication or network-level controls.

Recommended fix Moderate confidence

Latest stable WPGraphQL release (1.16.0 or later, check wordpress.org for current version)

  1. 1. Back up your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find WPGraphQL in the plugin list
  4. 4. If there is an update available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, you can manually download the latest WPGraphQL version from the official WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, test your GraphQL endpoint to ensure functionality is intact
  7. 7. Verify the update was successful by checking the WPGraphQL version in your plugins list
Caveat Minor version updates typically don't introduce breaking changes, but always review the changelog before updating

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

Fix this in Wpgraphql Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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