Quick answers
- Is CVE-2026-126061 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126061 being exploited in the wild.
- How severe is CVE-2026-126061?
- Medium severity, with a CVSS score of 4.3, published 10 November 2026.
- Which products and versions are affected?
- Winter CMS 1.2.13.
- Is there a fix for CVE-2026-126061?
- Yes: fixed in 1.2.14. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126061 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-126061?
- Check whether you run Winter CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.2.14
Technical details
The MyAccount controller in versions 1.2.13 inherits FormController actions (create, update, preview) with an empty $requiredPermissions array. The formFindModelObject() method resolves user identifiers through an unscoped Backend\Models\User query, allowing authenticated users to enumerate and read other users' profile attributes by crafting requests to /backend/myaccount/preview/{user_id}. Authorization guards prevent cross-user writes, but read access is not restricted.
Affected products
- Winter CMS Winter CMS 1.2.13
Timeline
- 2026-11-10: disclosed
- 2026-11-19: patched: Version 1.2.14 released with hardening of MyAccount controller