CVE-2026-54768: medium-severity vulnerability in wp-graphql
WPGraphQL has deprecated `user` field on SendPasswordResetEmailPayload that leaks user existence + profile (defeats explicit anti-enumeration design)
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.9epss 0.4%
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.
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
Affected products
wp-graphql · wp-graphqlRelated CVEs — wp-graphql
In the same product, most dangerous first.
CVE-2026-27938HIGHWPGraphQL Repo Vulnerable to Command Injection via Unsanitized GitHub Actions Expression in Release WorkflowEPSS 0.9%CVE-2026-88974MEDIUMWPGraphQL: Contributor can publish and modify posts without the required capabilities via updatePostEPSS 0.4%CVE-2026-33290MEDIUMWPGraphQL Repo's updateComment allows low-privileged authenticated users to change comment moderation status (comment_approved) without moderate_comments permissionEPSS 0.2%