WPGraphQL
WPGraphQL has 9 disclosed vulnerabilities in the WordSec catalog, reported between 2019 and 2026; all 9 are fixed as of September 2026. Their average CVSS score is 6.4, and the most serious one scores 9.8 out of 10. Severity breakdown: 2 critical and 1 high. 2019 was the busiest year with 4 disclosures.
The most common weakness is Missing Authorization, behind 2 of the records (22%). Other recurring categories include Cross-Site Request Forgery (CSRF), Exposure Of Sensitive Information To An Unauthorized Actor.
Every one of the 9 issues recorded for WPGraphQL has a vendor fix available, so running the current release closes all known holes.
7 independent researchers contributed these findings, most of them (3) reported by Simone Quatrini. WPGraphQL is installed on roughly 30,000 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 7.0.4.
CVE-2019-9879WPGraphQL <= 0.2.3 - Administrative User Creation
Read the full analysisVulnerability Records
WPGraphQL
Author
Jason Bahl
WPGraphQL is a free, open-source WordPress plugin that provides an extendable GraphQL schema and API for any WordPress site. Get Started Install WPGraphQL: wp plugin install wp-graphql --activate Try it out: Live Demo Read the Quick Start Guide. Join the Community on Discord and Star the Repo! Key Features Flexible API: Query posts, pages, custom post types, taxonomies, users, and more. Extendable Schema: Easily add functionality with WPGraphQL’s API, enabling custom integrations. Compatible with Modern Frameworks: Works seamlessly with Next.js, Astro, SvelteKit, and more. Optimized Performance: Fetch exactly the data you need in a single query. Boost performance with WPGraphQL Smart Cache. WPGraphQL is becoming a Canonical Plugin on WordPress.org, ensuring long-term support and a growing community of users and contributors. Upgrading It is recommended that anytime you want to update WPGraphQL that you get familiar with what’s changed in the release. WPGraphQL publishes release notes on Github. WPGraphQL has been following Semver practices for a few years. We will continue to follow Semver and let version numbers communicate meaning. The summary of Semver versioning is as follows: MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards compatible manner, and PATCH version when you make backwards compatible bug fixes. You can read more about the details of Semver at semver.org Privacy Policy WPGraphQL uses Appsero SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster and make product improvements. Appsero SDK does not gather any data by default. The SDK starts gathering basic telemetry data only when a user allows it via the admin notice. When you opt in, each telemetry request is sent to Appsero and a duplicate is sent in a non-blocking request to WPGraphQL-operated infrastructure at https://telemetry.wpgraphql.com (the same categories of data as described for Appsero below). Learn more about how Appsero collects and uses this data.
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C