WPGraphQL provides a GraphQL API for WordPress sites. From 2.0.0 until 2.15.1, the deprecated user field on SendPasswordResetEmailPayload lets an unauthenticated caller distinguish existing author-class accounts through the sendPasswordResetEmail mutation and obtain public profile fields. This issue is fixed in version 2.15.1.
CVE-2026-54768
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 62(Attend)EG Risk 62/100SSVC: Attend
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 computedSeverity69% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
July 31, 2026
Last Modified
August 3, 2026
Advisory Details (1)
Auto-updated Jul 31, 2026Deprecated `user` field on SendPasswordResetEmailPayload leaks user existence + profile (defeats explicit anti-enumeration design) · Advisory · wp-graphql/wp-graphql · GitHub
Affected: 2.10.0)
https://github.com/wp-graphql/wp-graphql/security/advisories/GHSA-jhh7-832h-f8hvVendor Advisories for CVE-2026-54768(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| composer | wp-graphql/wp-graphql | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| wp-graphql/wp-graphql | 0.0.2 ... v2.6.0 (239 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 59× 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.
- 2026-08-20 00:04 UTCEG score recompute
- 2026-08-20 00:03 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:15 UTCEG score recompute
- 2026-08-18 22:15 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 20:21 UTCEG score recompute
- 2026-08-17 20:21 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 18:35 UTCEG score recompute
- 2026-08-16 18:35 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 16:49 UTCEG score recompute
- 2026-08-15 16:49 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 15:02 UTCEG score recompute
- 2026-08-14 15:02 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 13:16 UTCEG score recompute
- 2026-08-13 13:16 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 11:30 UTCEG score recompute
- 2026-08-12 11:30 UTCGHSA enrichment
- 2026-08-11 09:44 UTCEG score recompute
Show 34 moreShow fewer
- 2026-08-11 09:43 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 07:56 UTCEG score recompute
- 2026-08-10 07:56 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 06:10 UTCEG score recompute
- 2026-08-09 06:10 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 04:24 UTCEG score recompute
- 2026-08-08 04:24 UTCGHSA enrichment
- 2026-08-07 02:38 UTCEG score recompute
- 2026-08-07 02:38 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 00:52 UTCEG score recompute
- 2026-08-06 00:52 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 23:06 UTCEG score recompute
- 2026-08-04 23:06 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 21:20 UTCEG score recompute
- 2026-08-03 21:20 UTCGHSA enrichment
- 2026-08-03 20:43 UTCEG score recompute
- 2026-08-03 20:43 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-03 03:04 UTCEG score recompute
- 2026-08-03 03:03 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-02 01:17 UTCGHSA enrichment
- 2026-07-31 23:31 UTCEG score recompute
- 2026-07-31 23:30 UTCGHSA enrichment
- 2026-07-31 22:48 UTCEG score recompute
- 2026-07-31 22:48 UTCGHSA enrichment
- 2026-07-31 22:48 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-54768?
When was CVE-2026-54768 disclosed?
Is CVE-2026-54768 actively exploited?
What is the CVSS score of CVE-2026-54768?
How do I remediate CVE-2026-54768?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54768
Is Your Infrastructure Affected by CVE-2026-54768?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.