# WPGraphQL has deprecated \`user\` field on SendPasswordResetEmailPayload that leaks user existence + profile (defeats explicit anti-enumeration design)

Advisory record · `GHSA-jhh7-832h-f8hv`

- **Identifiers:** `GHSA-jhh7-832h-f8hv` · `CVE-2026-54768` · `PKSA-2dkq-4nxk-nkts`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-204](https://cwe.mitre.org/data/definitions/204.html)
- **Tags:** [CWE-204](https://agentprime.io/advisories/tag/cwe-204.md)
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 31 Jul 2026, 22:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wp-graphql/wp-graphql` (Packagist): affected `<=2.6.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The wp-graphql/wp-graphql Packagist package, versions up to and including 2.6.0, is affected. A deprecated \`user\` field on the sendPasswordResetEmail payload returns a full user object when a supplied username or email matches an existing author-class user and null otherwise, which lets an unauthenticated attacker enumerate accounts and read public profile fields. No fixed version is listed.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0044, the 38th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jhh7-832h-f8hv)

## Sources

- [GitHub Advisory Database: GHSA-jhh7-832h-f8hv](https://github.com/advisories/GHSA-jhh7-832h-f8hv)
- [OSV: GHSA-jhh7-832h-f8hv](https://osv.dev/vulnerability/GHSA-jhh7-832h-f8hv)
- <https://github.com/wp-graphql/wp-graphql/security/advisories/GHSA-jhh7-832h-f8hv>
- <https://github.com/wp-graphql/wp-graphql>
- <https://github.com/wp-graphql/wp-graphql/releases/tag/wp-graphql/v2.15.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jhh7-832h-f8hv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jhh7-832h-f8hv/>. Everything for agents: <https://agentprime.io/llms.txt>.