{"answers":{"affected":"4 open source packages ship an affected version, including statamic/cms.","exploited":"There is no known exploitation of CVE-2026-49287 in the wild and no public exploit code.","fix":"Upgrade statamic/cms to a fixed version for your release line: 5.73.23 or 6.20.0.","what":"CVE-2026-49287 is a high-severity code injection vulnerability in statamic cms, published on 19 Jun 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-49287 and fix it if it is affected.\n\nWhat it is: CVE-2026-49287 is a high-severity code injection vulnerability in statamic cms, published on 19 Jun 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-49287 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- statamic/cms (Packagist): affected all versions; fixed in 5.73.23\n- statamic/cms (Packagist): affected all versions; fixed in 5.73.23\n- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.20.0\n- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.20.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-49287/ (Markdown: https://insights.sbomify.com/CVE-2026-49287/index.md)","id":"CVE-2026-49287","markdown":"https://insights.sbomify.com/CVE-2026-49287/index.md","name":"CVE-2026-49287","record":{"aliases":["GHSA-m92m-r54r-x8r2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Statamic CMS","requires_auth":"none","summary":"Attackers can destroy content and assets via unsafe method invocation in collection sorting if templates pass user input to sort parameters.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-470","name":"Use of Externally-Controlled Input to Select Classes or Code"}],"description":"Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.23 and 6.20.0, the fix for CVE-2026-41175 was incomplete. It addressed the issue in the query builder, but the same protection was not applied to in-memory collection sorting. Manipulating sort parameters could result in the loss of content and assets. This requires a front-end template that passes request input into a tag's sort parameter. It is not exploitable by default — a template would need to be explicitly set up to sort by a visitor-controlled value. This has been fixed in 5.73.23 and 6.20.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 CMS vulnerable to unsafe method invocation via collection sorting allows data destruction","id":"CVE-2026-49287","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"Statamic CMS missing authorization on Control Panel fieldtype endpoints allows disclosure of restricted resources","id":"CVE-2026-49288"},"packages":[{"ecosystem":"Packagist","fixed":["5.73.23"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-m92m-r54r-x8r2"},{"ecosystem":"Packagist","fixed":["5.73.23"],"introduced":["0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-m92m-r54r-x8r2"},{"ecosystem":"Packagist","fixed":["6.20.0"],"introduced":["6.0.0"],"last_affected":[],"package":"statamic/cms","purl":null,"source":"GHSA-m92m-r54r-x8r2"},{"ecosystem":"Packagist","fixed":["6.20.0"],"introduced":["6.0.0"],"last_affected":[],"package":"statamic/cms","purl":"pkg:composer/statamic/cms","source":"GHSA-m92m-r54r-x8r2"}],"prev":{"headline":"PhpWeasyPrint vulnerable to PHAR deserialization via output filename (CVE-2023-28115 case-insensitive bypass)","id":"CVE-2026-49286"},"products":["cms"],"published":"2026-06-19","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-06-22","vendors":["statamic"]},"summary":"Attackers can destroy content and assets via unsafe method invocation in collection sorting if templates pass user input to sort parameters.","url":"https://insights.sbomify.com/CVE-2026-49287/"}