{"answers":{"affected":"4 open source packages ship an affected version, including statamic/cms.","exploited":"There is no known exploitation of CVE-2026-64664 in the wild and no public exploit code.","fix":"Upgrade statamic/cms to a fixed version for your release line: 5.74.1 or 6.24.0.","what":"CVE-2026-64664 is a medium-severity vulnerability in statamic cms, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64664 and fix it if it is affected.\n\nWhat it is: CVE-2026-64664 is a medium-severity vulnerability in statamic cms, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-64664 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- statamic/cms (Packagist): affected all versions; fixed in 5.74.1\n- statamic/cms (Packagist): affected all versions; fixed in 5.74.1\n- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.24.0\n- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.24.0\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-64664/ (Markdown: https://insights.sbomify.com/CVE-2026-64664/index.md)","id":"CVE-2026-64664","markdown":"https://insights.sbomify.com/CVE-2026-64664/index.md","name":"CVE-2026-64664","record":{"aliases":["GHSA-225x-3jhx-wh4q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Statamic CMS","requires_auth":"low_privilege","summary":"Authenticated users can determine if email addresses exist in the system without proper authorization, leaking user existence data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.74.1 and 6.24.0, an authenticated Control Panel user could use an endpoint intended for the user creation wizard to determine if a given email address belonged to an existing user, without having permission to view users, though the endpoint only exposed user existence and not any other user data. This issue is fixed in versions 5.74.1 and 6.24.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Statamic: Missing authorization on Control Panel endpoint allows disclosure of user existence","id":"CVE-2026-64664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"Statamic: Account takeover via OAuth email matching without email-verification check","id":"CVE-2026-64665"},"packages":[{"ecosystem":"Packagist","fixed":["5.74.1"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-225x-3jhx-wh4q"},{"ecosystem":"Packagist","fixed":["5.74.1"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-225x-3jhx-wh4q"},{"ecosystem":"Packagist","fixed":["6.24.0"],"introduced":["6.0.0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-225x-3jhx-wh4q"},{"ecosystem":"Packagist","fixed":["6.24.0"],"introduced":["6.0.0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-225x-3jhx-wh4q"}],"prev":{"headline":"Statamic: Unsafe method invocation via Antlers template resolution allows data destruction","id":"CVE-2026-64663"},"products":["cms"],"published":"2026-08-06","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["statamic"]},"summary":"Authenticated users can determine if email addresses exist in the system without proper authorization, leaking user existence data.","url":"https://insights.sbomify.com/CVE-2026-64664/"}