winter/wn-backend-module
Affected
- introduced
1.2.0, fixed1.2.12(ecosystem)
Fixed versions
1.2.12
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-27591
Winter vulnerable to privilege escalation by authenticated backend users
Impact
Affected versions of Winter CMS allowed authenticated backend users to escalate their accounts level of access to the system by modifying the roles / permissions assigned to their account through specially crafted requests to the backend while logged in.
To actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.
The Winter CMS maintainers strongly recommend that all Winter CMS sites that have any reliance on the roles & permissions system to update immediately. Security fixes have been backported to all major versions of Winter (1.0, 1.1, and 1.2).
Patches
Multiple fixes and defence in depth has been applied to prevent current and future privilege escalation attacks at the lowest level possible.
This security issue has been fixed as of https://wintercms.com/releases/v1.0.477, https://wintercms.com/releases/v1.1.12, https://wintercms.com/releases/v1.2.12.
Workarounds
If you cannot upgrade, you may apply the changes from the releases to your Winter CMS installation manually to resolve this issue.
Critical Basis: The source's own band: CRITICAL
1.2.0, fixed 1.2.12 (ecosystem)1.2.12
The export has no generic command for this ecosystem.
1.1.0, fixed 1.1.12 (ecosystem)1.1.12
The export has no generic command for this ecosystem.
0, fixed 1.0.477 (ecosystem)1.0.477
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0