{"answers":{"affected":"2 open source packages ship an affected version, including wp-graphql/wp-graphql.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54768 exists.","fix":"No fix has been published for CVE-2026-54768 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54768 is a medium-severity vulnerability in wp-graphql, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54768 and fix it if it is affected.\n\nWhat it is: CVE-2026-54768 is a medium-severity vulnerability in wp-graphql, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54768 exists.\n\nAffected packages and fixed versions:\n- wp-graphql/wp-graphql (Packagist): affected all versions up to 2.6.0; no fix listed\n- wp-graphql/wp-graphql (Packagist): affected all versions up to 2.6.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54768/ (Markdown: https://insights.sbomify.com/CVE-2026-54768/index.md)","id":"CVE-2026-54768","markdown":"https://insights.sbomify.com/CVE-2026-54768/index.md","name":"CVE-2026-54768","record":{"aliases":["GHSA-jhh7-832h-f8hv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress GraphQL plugin","requires_auth":"none","summary":"Unauthenticated attackers can enumerate existing author accounts and retrieve public profile data via the password reset mutation, bypassing anti-enumeration controls.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"WPGraphQL has deprecated `user` field on SendPasswordResetEmailPayload that leaks user existence + profile (defeats explicit anti-enumeration design)","id":"CVE-2026-54768","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Langroid: Sandbox Escape to Remote Code Execution via Incomplete `eval()` Mitigation in TableChatAgent","id":"CVE-2026-54769"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["2.6.0"],"package":"wp-graphql/wp-graphql","purl":null,"source":"GHSA-jhh7-832h-f8hv"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["2.6.0"],"package":"wp-graphql/wp-graphql","purl":"pkg:composer/wp-graphql/wp-graphql","source":"GHSA-jhh7-832h-f8hv"}],"prev":{"headline":"WeGIA: Hardcoded Secret Key Backdoor — Mass Data Destruction via deletar_socios.php","id":"CVE-2026-54767"},"products":["wp-graphql"],"published":"2026-07-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["wp-graphql"]},"summary":"Unauthenticated attackers can enumerate existing author accounts and retrieve public profile data via the password reset mutation, bypassing anti-enumeration controls.","url":"https://insights.sbomify.com/CVE-2026-54768/"}