CVE-2019-25060: The WPGraphQL WordPress plugin before 0.3.5 doesn't properly restrict access to information about other users'

Q: How do I fix CVE-2019-25060?

wpgraphql: upgrade to 0.3.5. Exact commands for each OS are on this page.

Q: Is CVE-2019-25060 being exploited?

CVE-2019-25060 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-25060 affect?

CVE-2019-25060 affects wpgraphql. Severity is medium (CVSS 5.3). The WPGraphQL WordPress plugin before 0.3.5 doesn't properly restrict access to information about other users' roles on the affected site. Because of this, a remote attacker could forge a GraphQL query to retrieve the account roles of every

Q: How urgent is CVE-2019-25060?

Priority 48/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.3REMOTEUPGRADE

CVE-2019-25060 is a medium-severity flaw (CVSS 5.3) affecting wpgraphql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WPGraphQL WordPress plugin before 0.3.5 doesn't properly restrict access to information about other users' roles on the affected site. Because of this, a remote attacker could forge a GraphQL query to retrieve the account roles of every user on the site.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 21%)
CISA exploited list	No
Weakness	CWE-284
Published	2022-05-09
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wpgraphql

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-05-09 17:15 UTCPublished CVE record published
2026-06-17 02:31 UTCUpdated Record last modified

wpgraphql wpgraphql UPGRADE

Affected: < 0.3.5

Fixed in: 0.3.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wpgraphql || rpm -q wpgraphql || wpgraphql --version

2. UPGRADE to 0.3.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wpgraphql

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wpgraphql

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-25060?

wpgraphql: upgrade to 0.3.5. Exact commands for each OS are on this page.

Is CVE-2019-25060 being exploited?

CVE-2019-25060 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-25060 affect?

CVE-2019-25060 affects wpgraphql. Severity is medium (CVSS 5.3). The WPGraphQL WordPress plugin before 0.3.5 doesn't properly restrict access to information about other users' roles on the affected site. Because of this, a remote attacker could forge a GraphQL query to retrieve the account roles of every

How urgent is CVE-2019-25060?

Priority 48/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-23684 MEDIUM 4.4 UPGRADE Server-Side Request Forgery (SSRF) vulnerability in WPGraphQL.This issue affects WPGraphQL: from n/a through 1

References

← Back to latest CVEs