Read the docs

Winter CMS My Account preview exposes other backend users' profiles

Priority LOW 20CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

Winter CMS from 1.2.13 before 1.2.14 lets any authenticated backend user read another user's profile data by changing a record identifier in the My Account preview route. The MyAccount controller inherits form actions without a required permission and does not scope the user lookup to the current account. An attacker with a backend login can read names, logins, email addresses, avatars, roles, group memberships, superuser status and throttle state of other users, but cannot read password material or change other accounts. This issue is tracked as CWE-639, authorization bypass through a user-controlled key.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

Winter CMS is a content management system built on the Laravel PHP framework. From 1.2.13 until 1.2.14, the Backend\Controllers\MyAccount controller inherits the FormController actions create, update, and preview while declaring an empty $requiredPermissions array, and formFindModelObject() resolves a caller-supplied record identifier through an unscoped Backend\Models\User query. Any authenticated backend user can request another sequential user identifier through /backend/backend/myaccount/preview/{other_user_id} or the inherited update action and read profile data including name, login, email, avatar, role, group membership, superuser status, and throttle state. Password material is not exposed, and existing model authorization guards block cross-user writes. This issue is fixed in version 1.2.14.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00253 16th percentileScored 2026-11-16
Fix Fixed winter (wintercms): 1.2.14

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
wintercmswinter1.2.13 to before 1.2.141.2.14Patch availableCNA
  • winter Vendorwintercms Affected 1.2.13 to before 1.2.14 Fixed in 1.2.14 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:wintercms:winter:*:*:*:*:*:*:*:*——wintercms
  • cpe:2.3:a:wintercms:winter:*:*:*:*:*:*:*:* Versions — — ·wintercms

Remediation

Upgrade Winter CMS winter to version 1.2.14, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

  • Fix · CNA winter (wintercms) Fixed in 1.2.14

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-126061
  2. 2026-11-14 CISA SSVC decision points changed

References

  • TI-2024-19497 Server-side Template Injection (SSTI) vulnerability in Winter CMS v.1.2.3 allows a remote… CVSS 3.1HIGH 7.2
  • TI-2023-28528 Winter CMS Local File Inclusion through Server Side Template Injection CVSS 3.1MEDIUM 5.4
  • TI-2022-18732 Winter vulnerable to Prototype Pollution in Snowboard framework CVSS 3.1CRITICAL 9.8
  • TI-2026-55251 Winter CMS before 1.2.13 Twig Sandbox Escape via SecurityPolicy CVSS 4.0CRITICAL 9.3
  • TI-2026-21979 Winter: Privilege escalation by authenticated backend users CVSS 3.1CRITICAL 10.0
  • TI-2024-21102 Dusk plugin may allow unfettered user authentication in misconfigured installs CVSS 3.1HIGH 8.8
See all 24 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences