PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-84794 craftcms CVE debrief

Craft CMS versions before 5.10.11 have a high-severity vulnerability (CVSS Score: 7.1) due to lack of authorization checks in the assets/move-asset endpoint. This allows authenticated users without peer asset permissions to move assets into other users' folders and force deletion of conflicting files, enabling unauthorized asset deletion and replacement. Organizations should prioritize patching to prevent this vulnerability. The vulnerability affects operators, platforms, and security teams managing Craft CMS deployments. They should review and update asset permissions, monitor for unauthorized asset changes, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Compensating controls for exposed systems should be reviewed while remediation is scheduled and verified. Relevant monitoring, detection, and logs for exposed assets should be checked for extra review. Exceptions, retest remediated assets, and close the item only after evidence is documented. Asset inventory management is crucial to ensure all affected systems are accounted for and remediated properly. Rollback and change windows should be considered for updates to minimize operational impact. Source tracking is also essential to verify the effectiveness of the remediation efforts and to detect potential future vulnerabilities.

Vendor
craftcms
Product
cms
CVSS
HIGH 7.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-02
Original CVE updated
2026-09-04
Advisory published
2026-09-02
Advisory updated
2026-09-04

Who should care

Organizations using Craft CMS versions before 5.10.11 should prioritize patching to prevent unauthorized asset deletion and replacement. This vulnerability affects operators, platforms, and security teams responsible for managing Craft CMS deployments. They should review and update asset permissions, monitor for unauthorized asset changes, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Compensating controls for exposed systems should be reviewed while remediation is scheduled and verified. Relevant monitoring, detection, and logs for exposed assets should be checked for extra review. Exceptions, retest remediated assets, and close the item only after evidence is documented. Asset inventory management is crucial in this context to ensure all affected systems are accounted for and remediated properly. Rollback and change windows should be considered for updates to minimize operational impact. Source tracking is also essential to verify the effectiveness of the remediation efforts and to detect potential future vulnerabilities. Security teams should work closely with system administrators to implement these measures effectively and to maintain the security posture of their Craft CMS environments. The vulnerability's impact on the security team includes the need for heightened monitoring and potential adjustments to incident response plans. Overall, a coordinated effort is required to address this vulnerability and protect against potential exploitation. The role of the security team in this process is critical, as they must ensure that all necessary steps are taken to mitigate the vulnerability and maintain the security of the Craft CMS deployments. This involves not only technical measures but also communication and coordination with other stakeholders to ensure a comprehensive approach to vulnerability management. By prioritizing patching and taking proactive measures, organizations can reduce the risk associated with this vulnerability and protect their assets from potential exploitation. The importance of asset inventory management in this context cannot be overstated, as it is essential for ensuring

Technical summary

Craft CMS versions before 5.10.11 have a high-severity vulnerability (CVSS Score: 7.1) due to lack of authorization checks in the assets/move-asset endpoint. Authenticated users without peer asset permissions can move assets into other users' folders and force deletion of conflicting files, allowing unauthorized asset deletion and replacement. This vulnerability affects organizations using Craft CMS versions before 5.10.11.

Defensive priority

Organizations using Craft CMS versions before 5.10.11 should prioritize patching to prevent unauthorized asset deletion and replacement.

Recommended defensive actions

  • Patch Craft CMS to version 5.10.11 or later
  • Review and update asset permissions
  • Monitor for unauthorized asset changes
  • Verify asset permissions and monitor for unauthorized changes
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Consider rollback and change windows for updates to minimize operational impact
  • Implement source tracking to verify the effectiveness of the remediation efforts

Evidence notes

Evidence is limited; primary official records indicate Craft CMS versions before 5.10.11 lack authorization checks in the assets/move-asset endpoint. Users without peer asset permissions can move assets into other users' folders and force deletion of conflicting files. Defenders should verify asset permissions and monitor for unauthorized changes.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-84794 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-84794

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-84794 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-84794

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.