{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92594 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92594 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92594 is a high-severity vulnerability in craftcms cms, published on 16 Sep 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-92594 and fix it if it is affected.\n\nWhat it is: CVE-2026-92594 is a high-severity vulnerability in craftcms cms, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92594 in the wild and no public exploit code.\n\nAffected product: craftcms cms. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-92594/ (Markdown: https://insights.sbomify.com/CVE-2026-92594/index.md)","id":"CVE-2026-92594","markdown":"https://insights.sbomify.com/CVE-2026-92594/index.md","name":"CVE-2026-92594","record":{"aliases":["GHSA-f53v-9r85-mf77","GHSA-pcmv-c398-gc5m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Craft CMS","requires_auth":"none","summary":"Unauthenticated attackers can harvest PII of draft creators via GraphQL if public schema with draft scopes is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Craft CMS 5.0.0-RC1 through versions before 5.11.0 incorrectly authorize the GraphQL draftCreator and revisionCreator fields: instead of requiring the user-data scope enforced by Gql::canQueryUsers() (usergroups.*:read), these fields are gated only on the elements.drafts:read / elements.revisions:read scopes, and their resolver returns a raw User element whose email, username, fullName, and addresses fields have no per-field authorization. A client holding only the drafts or revisions scope — including an unauthenticated client when the operator has enabled the public GraphQL schema with those scopes — can therefore harvest the email addresses, usernames, full names, and postal addresses of all draft/revision creators (typically site editors and administrators). The issue is fixed in 5.11.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Craft CMS before 5.11.0 Unauthenticated PII Disclosure via GraphQL","id":"CVE-2026-92594","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Nodemailer before 9.1.1 Security Sandbox Bypass via resolveContent","id":"CVE-2026-92595"},"packages":[],"prev":{"headline":"Craft CMS 5.10.0 before 5.10.13 Authenticated Remote Code Execution","id":"CVE-2026-92593"},"products":["cms"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["craftcms"]},"summary":"Unauthenticated attackers can harvest PII of draft creators via GraphQL if public schema with draft scopes is enabled.","url":"https://insights.sbomify.com/CVE-2026-92594/"}