WPGraphQL: known security problems
10 known security problems reported for this WordPress plugin, with the affected versions, the fix and what to do.
Updated
In short
There are 10 known security problems on this page. 9 of them have a fixed version. Updating to version 2.11.1 or newer covers every fixed problem listed here.
Based on public reports. Check the plugin’s changelog. Watchfox AI may be wrong.
Get an email when your site is affected: install Watchfox AI (free)
A stranger could use it to harm your site (up to and including 2.24.0)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.24.0
- Fixed in
- No fixed version yet
- What to do
- There is no fixed version yet. If your site uses it, think about turning it off or replacing it until a fix comes out.
- Official ID
- CVE-2026-109703
- Report title
- WPGraphQL <= 2.24.0 - Unauthenticated Information Exposure
- First reported
- Sources
- Wordfence, seen
Someone could trick a logged-in admin into changing settings without knowing
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.5.3
- Fixed in
- 2.5.4
- What to do
- If your site has an affected version, update WPGraphQL to version 2.5.4 or newer.
- Official ID
- CVE-2025-68604
- Report title
- WPGraphQL <= 2.5.3 - Cross-Site Request Forgery
- First reported
- Sources
- Wordfence, seen
A stranger could read or change the data in your site’s database
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Before 2.11.1
- Fixed in
- 2.11.1
- What to do
- If your site has an affected version, update WPGraphQL to version 2.11.1 or newer.
- Official ID
- CVE-2026-40762
- Report title
- WPGraphQL < 2.11.1 - Unauthenticated SQL Injection
- First reported
- Sources
- Wordfence, seen
Someone could do things on your site they should not be allowed to
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 2.9.1
- Fixed in
- 2.10
- What to do
- If your site has an affected version, update WPGraphQL to version 2.10 or newer.
- Official ID
- CVE-2026-33290
- Report title
- WPGraphQL <= 2.9.1 - Missing Authorization
- First reported
- Sources
- Wordfence, seen
Someone with an editor account on your site could make your server visit other addresses on their behalf
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 1.14.5
- Fixed in
- 1.14.6
- What to do
- If your site has an affected version, update WPGraphQL to version 1.14.6 or newer.
- Official ID
- CVE-2023-23684
- Report title
- WPGraphQL <= 1.14.5 - Authenticated (Editor+) Server-Side Request Forgery
- First reported
- Sources
- Wordfence, seen
Someone could slow down or crash your site
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 1.3.5
- Fixed in
- 1.3.6
- What to do
- If your site has an affected version, update WPGraphQL to version 1.3.6 or newer.
- Official ID
- CVE-2021-31157
- Report title
- WPGraphQL <= 1.3.5 - Denial of Service
- First reported
- Sources
- Wordfence, seen
Someone could use it to harm your site (up to and including 0.3.4)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 0.3.4
- Fixed in
- 0.3.5
- What to do
- If your site has an affected version, update WPGraphQL to version 0.3.5 or newer.
- Official ID
- CVE-2019-25060
- Report title
- WPGraphQL <= 0.3.4 - Information Exposure
- First reported
- Sources
- Wordfence, seen
A stranger could use it to harm your site (up to and including 0.2.3)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 0.2.3
- Fixed in
- 0.3.0
- What to do
- If your site has an affected version, update WPGraphQL to version 0.3.0 or newer.
- Official ID
- CVE-2019-9881
- Report title
- WPGraphQL <= 0.2.3 - Unauthenticated Comment Creation
- First reported
- Sources
- Wordfence, seen
Someone could use it to harm your site (up to and including 0.2.3)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 0.2.3
- Fixed in
- 0.3.0
- What to do
- If your site has an affected version, update WPGraphQL to version 0.3.0 or newer.
- Official ID
- CVE-2019-9879
- Report title
- WPGraphQL <= 0.2.3 - Administrative User Creation
- First reported
- Sources
- Wordfence, seen
Someone could use it to harm your site (up to and including 0.2.3) (2)
A trusted security source confirmed it. If your site has an affected version, fix it this week.
- Affected versions
- Up to and including 0.2.3
- Fixed in
- 0.3.0
- What to do
- If your site has an affected version, update WPGraphQL to version 0.3.0 or newer.
- Official ID
- CVE-2019-9880
- Report title
- WPGraphQL <= 0.2.3 - Information Exposure
- First reported
- Sources
- Wordfence, seen
Where this comes from
We collect these reports from public security sources and rewrite them in plain words. Each problem shows its sources and the date we first saw it. This page never says whether your own site is affected: only a check of your site’s versions can tell.
Get an email when your site is affected.
Install Watchfox AI once. It checks your plugins and themes against this list every day, for free.
Install Watchfox AI (free)