Vulnerability Description
Winter CMS is a content management system built on the Laravel PHP framework. In versions prior to 1.2.13, the backend did not validate the handler name submitted through the form postback _handler POST field, allowing an authenticated backend user to invoke arbitrary controller methods, including protected, private, and action-prefixed ones. While AJAX requests validate that handler names match the on[A-Z][\w+]* pattern, the postback path passed the submitted _handler value straight to the handler dispatcher with no such check, so any controller that exposes a public action or conditionally relaxes its $requiredPermissions check could be reached, bypassing the roles and permissions system. The built-in Users controller was affected because it set $requiredPermissions to null for the myaccount action, letting any authenticated backend user invoke user-management methods such as update_onDelete and update_onManualPasswordReset without holding the backend.manage_users permission. This issue is fixed in version 1.2.13.
Related Weaknesses (CWE)
References
- https://github.com/wintercms/winter/pull/1473
- https://github.com/wintercms/winter/releases/tag/v1.2.13
- https://github.com/wintercms/winter/security/advisories/GHSA-j5jq-cr68-v2xx
FAQ
What is CVE-2026-35445?
CVE-2026-35445 is a documented vulnerability. Winter CMS is a content management system built on the Laravel PHP framework. In versions prior to 1.2.13, the backend did not validate the handler name submitted through the form postback _handler PO...
How severe is CVE-2026-35445?
CVSS scoring is not yet available for CVE-2026-35445. Check NVD for updates.
Is there a patch for CVE-2026-35445?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.