Answer in brief
CVE-2026-35445 records a High severity (CVSS 7.1) vulnerability in Winter: Authenticated backend users can bypass Users controller permission checks. The current sources do not mark it as known exploited. The current feed maps winter/wn-backend-module (composer), wintercms/winter (generic), winter/wn-backend-module (packagist). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps winter/wn-backend-module (composer), wintercms/winter (generic), winter/wn-backend-module (packagist). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| winter/wn-backend-modulecomposer | <=1.2.12 | 1.2.13 |
| wintercms/wintergeneric | < 1.2.13 | Not reported |
| winter/wn-backend-modulepackagist | >=0 <1.2.13 | 1.2.13 |
Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
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.
Quoted source text, attributed separately from HOL analysis.