Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Medium severity, with a CVSS score of 4.3, published 20 August 2026.

Which products and versions are affected?

winter/wn-backend-module (Packagist) = 1.2.13; Winter CMS WN Backend Module 1.2.13.

Is there a fix for This vulnerability?

A patch was published on 2026-08-20: Fixed in v1.2.14 with commit cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a software library.

Check whether you run winter/wn-backend-module (Packagist) or Winter CMS WN Backend Module 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.

Winter backend user profile information disclosure via MyAccount controller

Severity: medium · CVSS 4.3 · Published 2026-08-20

Winter CMS's backend account management feature allows authenticated administrators and staff members to view sensitive profile information of other backend users without proper authorization checks. An attacker with any level of backend access can enumerate all user accounts and retrieve their email addresses, names, roles, and security status. While passwords are masked, the exposed data enables account targeting and privilege mapping for further attacks.

Technologies: winter/wn-backend-module (Packagist), Winter CMS WN Backend Module. Vendors: Packagist, Winter CMS.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Medium severity, with a CVSS score of 4.3, published 20 August 2026.
Which products and versions are affected?: winter/wn-backend-module (Packagist) = 1.2.13; Winter CMS WN Backend Module 1.2.13.
Is there a fix for This vulnerability?: A patch was published on 2026-08-20: Fixed in v1.2.14 with commit cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run winter/wn-backend-module (Packagist) or Winter CMS WN Backend Module 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.

Technical details

The vulnerability is an authorization bypass (CWE-639) in the Backend\Controllers\MyAccount class. The FormController behavior exposes create, update, and preview actions that accept a user-supplied record ID via the URL. The formFindModelObject() method was not scoped to the authenticated user, allowing attackers to query the unscoped Backend\Models\User model. Exploitation requires network access and a valid backend user account (with any privilege level) but involves GET requests with no CSRF token requirement. Backend user IDs are sequential and trivially enumerated. The preview action discloses first name, last name, login, email, and avatar; the update action additionally exposes role, group membership, superuser flag, and throttle state. Write operations were blocked by authorization guards, so the confirmed impact is unauthorized information disclosure. Fixed in v1.2.14 by adding route guards and scoping form queries to the authenticated user.

Affected products

Winter CMS winter/wn-backend-module 1.2.13

Timeline

2026-08-20: disclosed: GHSA-mpmw-f6h6-3g26 published
2026-08-20: patched: Fixed in v1.2.14 with commit cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.