{"answers":{"affected":"2 open source packages ship an affected version, including statamic/cms. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27939 in the wild and no public exploit code.","fix":"Upgrade statamic/cms to 6.4.0 or later.","what":"CVE-2026-27939 is a high-severity vulnerability in statamic cms, published on 27 Feb 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-27939 and fix it if it is affected.\n\nWhat it is: CVE-2026-27939 is a high-severity vulnerability in statamic cms, published on 27 Feb 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-27939 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.4.0\n- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.4.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-27939/ (Markdown: https://insights.sbomify.com/CVE-2026-27939/index.md)","id":"CVE-2026-27939","markdown":"https://insights.sbomify.com/CVE-2026-27939/index.md","name":"CVE-2026-27939","record":{"aliases":["GHSA-rw9x-pxqx-q789"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Statamic CMS","requires_auth":"low_privilege","summary":"Authenticated users can bypass verification steps to gain elevated privileges and access sensitive operations in Statamic CMS.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"statamic","vendor":"statamic"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Statmatic is a Laravel and Git powered content management system (CMS). Starting in version 6.0.0 and prior to version 6.4.0, Authenticated Control Panel users may under certain conditions obtain elevated privileges without completing the intended verification step. This can allow access to sensitive operations and, depending on the user’s existing permissions, may lead to privilege escalation. This has been fixed in 6.4.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 allows Authenticated Control Panel users to escalate privileges via elevated session bypass","id":"CVE-2026-27939","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"llama.cpp has a Heap Buffer Overflow via Integer Overflow in `mem_size` Calculation — Bypass of CVE-2025-53630 Fix","id":"CVE-2026-27940"},"packages":[{"ecosystem":"Packagist","fixed":["6.4.0"],"introduced":["6.0.0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-rw9x-pxqx-q789"},{"ecosystem":"Packagist","fixed":["6.4.0"],"introduced":["6.0.0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-rw9x-pxqx-q789"}],"prev":{"headline":"WPGraphQL Repo Vulnerable to Command Injection via Unsanitized GitHub Actions Expression in Release Workflow","id":"CVE-2026-27938"},"products":["cms"],"published":"2026-02-27","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-45364","kev_date_added":null,"published":"2022-02-10"},{"cvss_score":9.3,"headline":"Statamic is vulnerable to account takeover via password reset link injection","id":"CVE-2026-27593","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":8.8,"headline":"Remote code execution via form uploads in statamic/cms","id":"CVE-2023-48217","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":8.8,"headline":"Statamic framework Incorrect Permission Assignment","id":"CVE-2017-11422","kev_date_added":null,"published":"2017-07-24"},{"cvss_score":8.7,"headline":"Statamic has Stored XSS via SVG Sanitization Bypass","id":"CVE-2026-33172","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.7,"headline":"Statamic vulnerable to privilege escalation via stored cross-site scripting","id":"CVE-2026-28426","kev_date_added":null,"published":"2026-02-27"}],"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":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["statamic"]},"summary":"Authenticated users can bypass verification steps to gain elevated privileges and access sensitive operations in Statamic CMS.","url":"https://insights.sbomify.com/CVE-2026-27939/"}