CVE-2026-35445

Winter: Authenticated backend users can bypass Users controller permission checks

Published Aug 26, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

In Winter CMS versions before 1.2.13, the handler name supplied by a backend user in the _handler POST field is not validated by the postback handler dispatcher. This omission allows the user to invoke any controller method—including private or protected methods—if the controller is reachable. The system’s permission checks can be bypassed because the dispatcher does not enforce the controller’s $requiredPermissions, permitting actions such as updating or deleting user accounts or resetting passwords without the required backend.manage_users right.

Affected Systems

Any installation of Winter CMS older than version 1.2.13 is vulnerable, particularly where the Users controller exposes public actions or relaxes permission checks.

Risk and Exploitability

The CVSS score of 7.1 marks this vulnerability as high severity. While an EPSS score is not available, the vulnerability is not listed in the CISA KEV catalog. The attack requires legitimate backend authentication but then sidesteps established role checks, making exploitation straightforward for any logged‑in user. The combination of a moderate-to-high severity score and minimal prerequisites suggests a notable risk to affected systems.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Winter CMS to version 1.2.13 or later to apply the fixed handler validation logic.
  • Re‑evaluate backend user roles to ensure users have only the permissions essential to their functions.
  • Implement network controls such as IP whitelisting or VPN access for backend management to reduce the attack surface for authenticated users.

Generated by OpenCVE AI on August 26, 2026 at 19:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-j5jq-cr68-v2xx Winter: Authenticated backend users can bypass Users controller permission checks
History
Type Values Removed Values Added
First Time appeared Wintercms
Wintercms winter
Vendors & Products Wintercms
Wintercms winter
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Winter: Authenticated backend users can bypass Users controller permission checks
Weaknesses CWE-285
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 26, 2026, 7:08 PM
Reserved
Apr 2, 2026, 7:25 PM
Status
Deferred
Published
Aug 26, 2026, 5:16 PM
Modified
Sep 9, 2026, 9:09 PM