WPGraphQL at a glance
- 11 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Nov 13, 2026.
- Ranked #923 by popularity on WordPress.org (30,000+ active installs).
- The latest version is 2.29.0 (released Nov 20, 2026). The most recent security fix shipped in 2.27.1.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your WPGraphQL version
Enter the WPGraphQL version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “WPGraphQL”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “WPGraphQL”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2.29.0). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known WPGraphQL vulnerabilities
WPGraphQL <= 2.27.0 - Authenticated (Contributor+) Information Exposure
Information disclosure · CVE-2026-123707
Affected versions: ≤ 2.27.0
Fixed in: 2.27.1
Severity: Medium 4.3 · Disclosed Nov 13, 2026
WPGraphQL <= 2.26.0 - Unauthenticated Information Exposure
Information disclosure · CVE-2026-109703
Affected versions: ≤ 2.26.0
Fixed in: 2.26.1
Severity: Medium 5.3 · Disclosed Oct 13, 2026
WPGraphQL <= 2.5.3 - Cross-Site Request Forgery
Cross-site request forgery (CSRF) · CVE-2025-68604
Affected versions: ≤ 2.5.3
Fixed in: 2.5.4
Severity: Medium 4.3 · Disclosed May 7, 2026
WPGraphQL < 2.11.1 - Unauthenticated SQL Injection
SQL injection · CVE-2026-40762
Affected versions: < 2.11.1
Fixed in: 2.11.1
Severity: High 7.5 · Disclosed Apr 21, 2026
WPGraphQL <= 2.9.1 - Missing Authorization
Missing authorization · CVE-2026-33290
Affected versions: ≤ 2.9.1
Fixed in: 2.10
Severity: Medium 4.3 · Disclosed Mar 24, 2026
WPGraphQL <= 1.14.5 - Authenticated (Editor+) Server-Side Request Forgery
Server-side request forgery (SSRF) · CVE-2023-23684
Affected versions: ≤ 1.14.5
Fixed in: 1.14.6
Severity: Medium 5.5 · Disclosed Jun 28, 2023
WPGraphQL <= 1.3.5 - Denial of Service
Other weakness · CVE-2021-31157
Affected versions: ≤ 1.3.5
Fixed in: 1.3.6
Severity: Medium 5.3 · Disclosed Apr 27, 2021
WPGraphQL <= 0.3.4 - Information Exposure
Missing authorization · CVE-2019-25060
Affected versions: ≤ 0.3.4
Fixed in: 0.3.5
Severity: Medium 6.5 · Disclosed Jul 10, 2019
WPGraphQL <= 0.2.3 - Administrative User Creation
Other weakness · CVE-2019-9879
Affected versions: ≤ 0.2.3
Fixed in: 0.3.0
Severity: Critical 9.8 · Disclosed May 8, 2019
WPGraphQL <= 0.2.3 - Information Exposure
Information disclosure · CVE-2019-9880
Affected versions: ≤ 0.2.3
Fixed in: 0.3.0
Severity: Critical 9.1 · Disclosed May 8, 2019
WPGraphQL <= 0.2.3 - Unauthenticated Comment Creation
Missing authorization · CVE-2019-9881
Affected versions: ≤ 0.2.3
Fixed in: 0.3.0
Severity: Medium 5.3 · Disclosed May 8, 2019
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| WPGraphQL <= 2.27.0 - Authenticated (Contributor+) Information ExposureInformation disclosure · CVE-2026-123707 | ≤ 2.27.0 | 2.27.1 | Medium 4.3 | Nov 13, 2026 |
| WPGraphQL <= 2.26.0 - Unauthenticated Information ExposureInformation disclosure · CVE-2026-109703 | ≤ 2.26.0 | 2.26.1 | Medium 5.3 | Oct 13, 2026 |
| WPGraphQL <= 2.5.3 - Cross-Site Request ForgeryCross-site request forgery (CSRF) · CVE-2025-68604 | ≤ 2.5.3 | 2.5.4 | Medium 4.3 | May 7, 2026 |
| WPGraphQL < 2.11.1 - Unauthenticated SQL InjectionSQL injection · CVE-2026-40762 | < 2.11.1 | 2.11.1 | High 7.5 | Apr 21, 2026 |
| WPGraphQL <= 2.9.1 - Missing AuthorizationMissing authorization · CVE-2026-33290 | ≤ 2.9.1 | 2.10 | Medium 4.3 | Mar 24, 2026 |
| WPGraphQL <= 1.14.5 - Authenticated (Editor+) Server-Side Request ForgeryServer-side request forgery (SSRF) · CVE-2023-23684 | ≤ 1.14.5 | 1.14.6 | Medium 5.5 | Jun 28, 2023 |
| WPGraphQL <= 1.3.5 - Denial of ServiceOther weakness · CVE-2021-31157 | ≤ 1.3.5 | 1.3.6 | Medium 5.3 | Apr 27, 2021 |
| WPGraphQL <= 0.3.4 - Information ExposureMissing authorization · CVE-2019-25060 | ≤ 0.3.4 | 0.3.5 | Medium 6.5 | Jul 10, 2019 |
| WPGraphQL <= 0.2.3 - Administrative User CreationOther weakness · CVE-2019-9879 | ≤ 0.2.3 | 0.3.0 | Critical 9.8 | May 8, 2019 |
| WPGraphQL <= 0.2.3 - Information ExposureInformation disclosure · CVE-2019-9880 | ≤ 0.2.3 | 0.3.0 | Critical 9.1 | May 8, 2019 |
| WPGraphQL <= 0.2.3 - Unauthenticated Comment CreationMissing authorization · CVE-2019-9881 | ≤ 0.2.3 | 0.3.0 | Medium 5.3 | May 8, 2019 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 13, 2026.
Most common weaknesses in WPGraphQL
Information disclosure
3 issues
Data that should stay private, such as user details or configuration values, can be read from outside.
Missing authorization
3 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Cross-site request forgery (CSRF)
1 issue
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Frequently asked questions
Is WPGraphQL safe to use?
WPGraphQL is a well-known plugin with 30,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.29.0) and turn on automatic updates.
How do I find which version of WPGraphQL my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.