NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

Improper Access Control in wp-graphqlGHSA-w3xg-7q6m-3xwp

MEDIUMFix: wp-graphql/wp-graphql#900

GHSA-w3xg-7q6m-3xwp is a medium-severity (CVSS 5.3) CWE-284 vulnerability in wp-graphql/wp-graphql. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for wp-graphql/wp-graphql — see the affected versions and patch details below.

Also known asCVE-2019-25060
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk
0.01%0.78%1.56%2.33%0.5%1.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐘wp-graphql/wp-graphql

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistwp-graphql/wp-graphqlall versions0.3.5composer require wp-graphql/wp-graphql:^0.3.5

Affected Products

1 product · 1 configurations
Application
wpgraphqlwpgraphql
< 0.3.5
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wp-graphql/wp-graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update wp-graphql/wp-graphql to 0.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w3xg-7q6m-3xwp is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-w3xg-7q6m-3xwp in your dependencies?

Find it across Packagist, including transitive dependencies.

Improper Access Control in wp-graphql (Medium 5.3)