CVE-2025-68604

WordPress WPGraphQL plugin <= 2.5.3 - Cross Site Request Forgery (CSRF) vulnerability

Published May 7, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
Cross-Site Request Forgery (CSRF) vulnerability in WPGraphQL allows Cross Site Request Forgery.

This issue affects WPGraphQL: from n/a through 2.5.3.

Analysis

AI-generated

Technical impact

This vulnerability is a Cross Site Request Forgery (CSRF) flaw that allows an attacker to cause a victim’s browser to perform unwanted actions on a WordPress site that uses the WPGraphQL plugin. The flaw stems from insufficient verification of requests and is classified as CWE-352. An attacker who tricks a logged‑in user into visiting a malicious page can potentially invoke GraphQL operations with the victim’s privileges, compromising the confidentiality, integrity, or availability of site data. The impact is limited to the scope of the victim’s authenticated session but can lead to unauthorized data modification or retrieval.

Affected Systems

The affected product is the WordPress WPGraphQL plugin, versions from the earliest releases up to and including 2.5.3. Any WordPress installation that has the WPGraphQL plugin installed at 2.5.3 or earlier is vulnerable. This includes sites that rely on the plugin’s GraphQL API endpoints to expose site data or functionality.

Risk and Exploitability

Based on the description, it is inferred that the likely attack vector is an HTTP request originating from an attacker’s domain that forces the victim’s authenticated browser to submit a GraphQL operation. The CVSS score of 5.4 indicates a medium severity. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog, suggesting that widespread exploitation has not yet been observed. However, because CSRF attacks typically require a victim who is already authenticated, the likelihood of exploitation depends on the attacker’s ability to create a phishing or embed a malicious link. The flaw can be exploited by sending a forged request from an attacker’s site to a victim’s WordPress site, leveraging the victim’s logged‑in session to perform GraphQL mutations. The lack of mandatory CSRF tokens at the plugin level makes this possible.

Remediation

Vendor Solution

Update the WordPress WPGraphQL Plugin to the latest available version (at least 2.5.4).


OpenCVE Recommended Actions

  • Update the WordPress WPGraphQL Plugin to version 2.5.4 or later, which removes the CSRF vulnerability.
  • If an update is not immediately possible, temporarily disable the WPGraphQL plugin until a patch is applied.
  • Restrict access to the GraphQL endpoint (e.g., via IP whitelisting or authentication checks) to reduce the attack surface while the plugin is in use.

Generated by OpenCVE AI on May 7, 2026 at 09:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Wordpress
Wordpress wordpress
Wpgraphql
Wpgraphql wpgraphql
Vendors & Products Wordpress
Wordpress wordpress
Wpgraphql
Wpgraphql wpgraphql
Type Values Removed Values Added
Description Cross-Site Request Forgery (CSRF) vulnerability in WPGraphQL allows Cross Site Request Forgery. This issue affects WPGraphQL: from n/a through 2.5.3.
Title WordPress WPGraphQL plugin <= 2.5.3 - Cross Site Request Forgery (CSRF) vulnerability
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
Patchstack
Published
Updated
May 7, 2026, 2:57 PM
Reserved
Dec 19, 2025, 10:20 AM
Status
Deferred
Published
May 7, 2026, 9:16 AM
Modified
Oct 14, 2026, 1:10 PM