CVE-2019-9880

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 35%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered in the WPGraphQL 0.2.3 plugin for WordPress. By querying the 'users' RootQuery, it is possible, for an unauthenticated attacker, to retrieve all WordPress users details such as email address, role, and username.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Track)
EG Risk 72/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.3%
KEV
Not listed

Published

June 10, 2019

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jul 18, 2026
Patch available. Sources: github_release.
generic

Pwning WordPress GraphQL | Pen Test Partners

https://www.pentestpartners.com/security-blog/pwning-wordpress-graphql/
github_release Patch Available

v0.3.0

Patch available: wp-graphql/wp-graphql v0.3.0 (pre-release)

https://github.com/wp-graphql/wp-graphql/releases/tag/v0.3.0
generic

snippets/wp-graphql0.2.3_exploit.py at master · pentestpartners/snippets · GitHub

https://github.com/pentestpartners/snippets/blob/master/wp-graphql0.2.3_exploit.py

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:15 UTCEPSS rescore
  2. 2026-07-23 14:15 UTCEPSS rescore
  3. 2026-07-23 01:47 UTCEG score recompute
  4. 2026-07-22 22:30 UTCEG score recompute
  5. 2026-07-22 14:05 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-21 15:22 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-20 14:34 UTCOSV refresh
  10. 2026-07-19 14:28 UTCEPSS rescore
  11. 2026-07-19 14:28 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-18 10:02 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-16 16:59 UTCEPSS rescore
  17. 2026-07-15 16:55 UTCEPSS rescore
  18. 2026-07-13 22:27 UTCEPSS rescore
  19. 2026-07-13 06:10 UTCEPSS rescore
  20. 2026-07-13 06:10 UTCEPSS rescore
  21. 2026-07-12 05:44 UTCEPSS rescore
  22. 2026-07-11 08:24 UTCEPSS rescore
  23. 2026-07-09 19:06 UTCEPSS rescore
  24. 2026-07-08 15:11 UTCEPSS rescore
  25. 2026-07-06 16:25 UTCEPSS rescore
Show 53 more
  1. 2026-07-06 16:25 UTCEPSS rescore
  2. 2026-07-04 06:28 UTCEPSS rescore
  3. 2026-07-03 09:56 UTCOSV refresh
  4. 2026-07-01 15:03 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-06-28 04:54 UTCEPSS rescore
  7. 2026-06-28 04:54 UTCEPSS rescore
  8. 2026-06-27 03:06 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-24 14:03 UTCEPSS rescore
  12. 2026-06-24 14:03 UTCEPSS rescore
  13. 2026-06-23 21:31 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-21 01:57 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-18 17:50 UTCEPSS rescore
  18. 2026-06-18 17:50 UTCEPSS rescore
  19. 2026-06-17 17:50 UTCEPSS rescore
  20. 2026-06-17 17:50 UTCEPSS rescore
  21. 2026-06-16 17:50 UTCEPSS rescore
  22. 2026-06-16 17:50 UTCEPSS rescore
  23. 2026-06-15 17:46 UTCEPSS rescore
  24. 2026-06-15 00:13 UTCOSV refresh
  25. 2026-06-14 23:15 UTCEPSS rescore
  26. 2026-06-14 23:15 UTCEPSS rescore
  27. 2026-06-13 22:58 UTCEPSS rescore
  28. 2026-06-13 22:58 UTCEPSS rescore
  29. 2026-06-12 23:09 UTCEPSS rescore
  30. 2026-06-11 13:58 UTCEPSS rescore
  31. 2026-06-10 22:16 UTCEPSS rescore
  32. 2026-06-10 22:16 UTCEPSS rescore
  33. 2026-06-10 13:20 UTCEPSS rescore
  34. 2026-06-08 14:15 UTCEPSS rescore
  35. 2026-06-08 14:15 UTCEPSS rescore
  36. 2026-06-07 15:23 UTCEPSS rescore
  37. 2026-06-07 15:23 UTCEPSS rescore
  38. 2026-06-06 13:45 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-06 13:45 UTCEPSS rescore
  41. 2026-06-05 06:08 UTCEPSS rescore
  42. 2026-06-02 20:11 UTCEPSS rescore
  43. 2026-06-02 20:11 UTCEPSS rescore
  44. 2026-06-01 13:50 UTCEPSS rescore
  45. 2026-06-01 13:50 UTCEPSS rescore
  46. 2026-05-31 00:14 UTCEPSS rescore
  47. 2026-05-31 00:14 UTCEPSS rescore
  48. 2026-05-29 13:42 UTCEPSS rescore
  49. 2026-05-27 18:33 UTCEG score recompute
  50. 2026-05-27 18:33 UTCGHSA enrichment
  51. 2026-05-27 13:39 UTCEPSS rescore
  52. 2026-05-27 13:38 UTCEPSS rescore
  53. 2026-05-24 16:47 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-46886
    First seen May 21, 2019

    WordPress Plugin WPGraphQL 0.2.3 - Multiple Vulnerabilities

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-9880.yaml
    First seen Jan 1, 2019

    WPEngine WPGraphQL 0.2.3 - Unauthenticated User Information Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-9880?
CVE-2019-9880 is a critical vulnerability published on June 10, 2019. An issue was discovered in the WPGraphQL 0.2.3 plugin for WordPress. By querying the 'users' RootQuery, it is possible, for an unauthenticated attacker, to retrieve all WordPress users details such as email address, role, and username.
When was CVE-2019-9880 disclosed?
CVE-2019-9880 was first published in the National Vulnerability Database on June 10, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-9880 actively exploited?
CVE-2019-9880 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-9880?
CVE-2019-9880 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2019-9880?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-9880, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-9880

Explore →

Is Your Infrastructure Affected by CVE-2019-9880?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs