CriticalGHSA-pgpf-m8m4-6cg6CVE-2026-27591

Winter vulnerable to privilege escalation by authenticated backend users

Published 12 Mar 2026 · Updated 14 Mar 2026

Is your project on an affected winter/wn-backend-module?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.2.0 <1.2.12
Fixed in
1.2.12
Update to the fixed version for your release line, for example:composer require winter/wn-backend-module:^1.2.12
Affected
>=1.1.0 <1.1.12
Fixed in
1.1.12
Update to the fixed version for your release line, for example:composer require winter/wn-backend-module:^1.1.12
Affected
<1.0.477
Fixed in
1.0.477
Update to the fixed version for your release line, for example:composer require winter/wn-backend-module:^1.0.477

Details

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.

Is GHSA-pgpf-m8m4-6cg6 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected winter/wn-backend-module, and gives you the command that fixes it.

More advisories for winter/wn-backend-module

  • MediumCVE-2026-125340Winter: Reflected XSS through the search query parameter in the backend Table widget · 20 Aug 2026
  • MediumCVE-2026-125339Winter: CSRF through AJAX handler names reachable as backend page actions · 20 Aug 2026
  • MediumCVE-2026-125338Winter: Stored XSS through cached Brand Settings and Editor Settings custom styles · 20 Aug 2026
  • HighCVE-2026-125337Winter: ImportExportController AJAX handlers bypass granular import/export permission gate · 20 Aug 2026
  • MediumCVE-2026-126061Winter: My Account preview exposes another backend user's profile by record ID · 20 Aug 2026
  • LowCVE-2026-125341Winter: Stored XSS through Backend List widget image columns · 20 Aug 2026
All 15 advisories for winter/wn-backend-module

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.