Skip to main content
VulnerabilityPublished

CVE-2026-35445: Winter · Authenticated backend users can bypass Users controller permission checks

Affects winter/wn-backend-moduleSource GCVE Database

0
Compare
Authoritative record:CVE-2026-35445· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 1.2.13 soon.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.13
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade winter/wn-backend-module to 1.2.13.

Affected software

ProductAffectedFixed in
Packagistwinter/wn-backend-moduleAffected
  • <1.2.13
Fixed in
  • 1.2.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Winter CMS backend module to version 1.2.13 or later, where this vulnerability is fixed. Applying this official patch eliminates the permission bypass issue. No additional mitigation is required once the update is applied.

Description

Winter CMS versions prior to 1.2.13 contain a vulnerability in the backend module where authenticated backend users can bypass permission checks on the Users controller. This occurs because the backend did not properly validate the _handler POST field, allowing invocation of arbitrary controller methods, including those normally protected. The Users controller was specifically affected due to a null $requiredPermissions setting on the myaccount action, enabling unauthorized user-management operations. The issue is fixed in version 1.2.13.

References

Community reviews

Loading reviews…