{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-49287", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-05-28T20:07:58.862Z", "datePublished": "2026-06-19T17:36:23.536Z", "dateUpdated": "2026-06-19T17:36:23.536Z"}, "containers": {"cna": {"title": "Statamic CMS vulnerable to unsafe method invocation via collection sorting allows data destruction", "problemTypes": [{"descriptions": [{"cweId": "CWE-470", "lang": "en", "description": "CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 7.4, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H", "version": "3.1"}}], "references": [{"name": "https://github.com/statamic/cms/security/advisories/GHSA-m92m-r54r-x8r2", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/statamic/cms/security/advisories/GHSA-m92m-r54r-x8r2"}, {"name": "https://github.com/statamic/cms/security/advisories/GHSA-4jjr-vmv7-wh4w", "tags": ["x_refsource_MISC"], "url": "https://github.com/statamic/cms/security/advisories/GHSA-4jjr-vmv7-wh4w"}], "affected": [{"vendor": "statamic", "product": "cms", "versions": [{"version": "< 5.73.23", "status": "affected"}, {"version": ">= 6.0.0, < 6.20.0", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-06-19T17:36:23.536Z"}, "descriptions": [{"lang": "en", "value": "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 \u2014 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."}], "source": {"advisory": "GHSA-m92m-r54r-x8r2", "discovery": "UNKNOWN"}}}}

{}

{}

{}

{}