dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-68604

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in WPGraphQL allows Cross Site Request Forgery. This issue affects WPGraphQL: from n/a through 2.5.3.

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

CSRF vulnerability in WPGraphQL allows attackers to induce authenticated users to execute unwanted GraphQL mutations. The lack of proper CSRF tokens or origin validation enables cross-site request forgery attacks against logged-in WordPress users.

MitigationImplement anti-CSRF token validation for GraphQL mutations and verify Origin/Referer headers. Apply SameSite attribute to authentication cookies.

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 WPGraphQL plugin is installed
    Check for the WPGraphQL plugin in wp-content/plugins/ directory, or look for the GraphQL endpoint at yoursite.com/graphql/
    Affected if WPGraphQL plugin is active and the /graphql/ endpoint is accessible
  2. Identify installed WPGraphQL version
    Open wp-content/plugins/wp-graphql/readme.txt and find the version in the header, or check the plugin main file for 'Version:' comment
    Affected if Version is lower than the patched version (check WPGraphQL changelog for the security fix release)
  3. Verify GraphQL mutations are executable
    Send a POST request to /graphql/ with a test mutation (e.g., {__typename}) without any CSRF token or nonce
    Affected if The endpoint accepts and processes mutations without requiring anti-CSRF tokens in the request headers or body
  4. Check authentication cookie attributes
    Inspect Set-Cookie headers for the WordPress session cookie; verify if SameSite attribute is set to 'Lax' or 'Strict'
    Affected if Authentication cookies lack SameSite attribute or are set to 'None' without secure flag
  5. Inspect WordPress CSRF protection configuration
    Check if wp-config.php has DISALLOW_FILE_MODPS or if the site validates Origin/Referer headers for GraphQL API requests
    Affected if No Origin/Referer header validation is performed for GraphQL endpoint requests

If WPGraphQL is installed and its /graphql/ endpoint accepts mutations without requiring CSRF tokens or validating request origins, the site is vulnerable to CVE-2025-68604.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF token validation for GraphQL mutations and verify Origin/Referer headers. Apply SameSite attribute to authentication cookies.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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