Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
Cross-Site Request Forgery (CSRF) vulnerability in WPGraphQL allows Cross Site Request Forgery.
This issue affects WPGraphQL: from n/a through 2.5.3.
AnalysisAI
Cross-site request forgery (CSRF) in WPGraphQL plugin versions up to 2.5.3 allows unauthenticated attackers to perform unauthorized actions on behalf of authenticated WordPress users with user interaction (typically clicking a malicious link). The vulnerability affects the GraphQL endpoint's lack of token-based request verification, enabling attackers to craft requests that WordPress site visitors are tricked into executing without their knowledge. No public exploit code or active exploitation has been confirmed.
Technical ContextAI
WPGraphQL is a WordPress plugin that exposes WordPress data and functionality through a GraphQL API endpoint. The vulnerability stems from insufficient CSRF protection on GraphQL requests (CWE-352: Cross-Site Request Forgery). GraphQL endpoints typically handle POST requests that modify data (mutations), and when CSRF tokens are not properly validated or are missing, attackers can forge requests from external sites. The plugin's CPE identifier (cpe:2.3:a:wpgraphql:wpgraphql:*:*:*:*:*:*:*:*) indicates this affects all versions through 2.5.3. Modern WordPress uses nonce-based CSRF protection; this vulnerability suggests WPGraphQL's GraphQL endpoint bypasses or insufficiently validates these nonces on certain mutations.
RemediationAI
Upgrade WPGraphQL plugin to version 2.5.4 or later immediately. The vendor advisory via Patchstack (https://patchstack.com/database/wordpress/plugin/wp-graphql/vulnerability/wordpress-wpgraphql-plugin-2-5-3-cross-site-request-forgery-csrf-vulnerability?_s_id=cve) provides patch information. If immediate upgrade is not feasible, implement WordPress security headers (SameSite=Strict on cookies) at the web server level to mitigate CSRF attacks site-wide; this affects all plugins but may break some cross-site integrations. Additionally, restrict GraphQL endpoint access to authenticated users only if your use case permits, using WordPress role-based capability checks on the GraphQL_Init hook. Monitor GraphQL mutation logs for unexpected requests originating from external referrers using a WordPress security plugin like Wordfence or Sucuri.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2025-209718
GHSA-655c-g9rr-96vv