GHSA-mpmw-f6h6-3g26: Winter My Account Preview Exposes Another Vulnerability

MODERATE
CVSS 4.3
CWE-639
Published
Advisory Summary

GHSA-mpmw-f6h6-3g26 is a MODERATE (CVSS 4.3) my account preview exposes another vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Winter libraries in the Packagist ecosystem. The issue involves my account preview exposes another backend user's profile by record id. Remediation is available by upgrading affected packages to version 1.2.14.

GHSA-mpmw-f6h6-3g26 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-mpmw-f6h6-3g26
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Winter
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix GHSA-mpmw-f6h6-3g26

To remediate this vulnerability, upgrade all affected Winter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

winter/wn-backend-module fixed: 1.2.14
Upgrade winter/wn-backend-module to 1.2.14
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for winter/wn-backend-module

How to Check if You Are Affected

To determine whether your application is affected by GHSA-mpmw-f6h6-3g26, inspect your project dependencies for Winter:

inspect dependencies for winter/wn-backend-module

Analyze the terminal output to locate any version of Winter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.14), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Winter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `Backend\Controllers\MyAccount`, introduced in v1.2.13, declares an empty `$requiredPermissions` array so that any authenticated backend user can manage their own account. It implements the `FormController` behavior, which exposes three routable actions — `create`, `update` and `preview` — that each take a record id from the URL. `index()` passes the authenticated user's own id to the behavior, but the inherited actions were left routable and `formFindModelObject()` was not scoped, so a caller-supplied id resolved against an unscoped `Backend\Models\User` query: ``` GET /backend/backend/myaccount/preview/{other_user_id} ``` `preview` disclosed the target user's first name, last name, login, email address and avatar; `update` was equally routable and additionally disclosed role, group membership, superuser flag and throttle state. Password controls render a mask, so no credential material was exposed. Backend user ids are sequential and trivially enumerated, and as these are `GET` actions no CSRF token is involved. The behavior's AJAX handlers (`create_onSave`, `update_onSave`, `update_onDelete`) were also dispatchable on these routes, but cross-user writes were blocked by the `Backend\Models\User` authorization guards added in v1.2.13. The confirmed impact is unauthorized disclosure of backend user profile data. To actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access. ### Patches `MyAccount` no longer exposes the generic record actions it never used as routes, and its form lookup is now pinned to the authenticated user: - `protected $guarded = ['create', 'update', 'preview'];` removes the inherited actions from routing. The guard has to be at the routing layer, as handler dispatch (`{action}_{handler}`) runs before the page action. - `formExtendQuery()` constrains every lookup made by the behavior to the current user's key. This security issue has been fixed as of **v1.2.14** (commit [`cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb`](https://github.com/wintercms/winter/commit/cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb)). ### Workarounds There is no supported workaround other than upgrading. If you cannot upgrade immediately, you may apply the fix manually in `modules/backend/controllers/MyAccount.php`: 1. Add `protected $guarded = ['create', 'update', 'preview'];` to the controller. 2. Add a `formExtendQuery()` method that scopes the lookup to the current user: ```php public function formExtendQuery(\Winter\Storm\Database\Builder $query): void { $query->whereKey($this->user->getKey()); } ``` ### References - https://github.com/wintercms/winter/security/advisories/GHSA-j5jq-cr68-v2xx - https://github.com/wintercms/winter/commit/cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb Credit to Awwader ([@NRAwwad](https://github.com/NRAwwad)) for reporting the issue. ### For more information If you have any questions or comments about this advisory: - Email us at [hello@wintercms.com](mailto:hello@wintercms.com)

GHSA-mpmw-f6h6-3g26 Affected Winter Versions

1 component(s)
Fixed Versions:
1.2.14
Product / Package Ecosystem Affected Versions Fixed Version
winter/wn-backend-module
Packagist
≥ 1.2.13
< 1.2.14
All 1 versions
1.2.13
1.2.14

References

Frequently Asked Questions

What is GHSA-mpmw-f6h6-3g26?
GHSA-mpmw-f6h6-3g26 is a security vulnerability in Winter involving My Account preview exposes another backend user's profile by record ID under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Winter versions are affected?
Affected versions include releases prior to 1.2.14 across affected packages: winter/wn-backend-module.
What version fixes GHSA-mpmw-f6h6-3g26?
Upgrading to 1.2.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is winter/wn-backend-module affected?
Yes, winter/wn-backend-module is affected in releases prior to 1.2.14. Upgrade your dependency to 1.2.14 or later.
What is the CVSS score of GHSA-mpmw-f6h6-3g26?
GHSA-mpmw-f6h6-3g26 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with GHSA-mpmw-f6h6-3g26?
GHSA-mpmw-f6h6-3g26 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Packagist dependencies for GHSA-mpmw-f6h6-3g26?
Run the dependency tree command: 'inspect dependencies for winter/wn-backend-module'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mpmw-f6h6-3g26",
  "modified" : "2026-08-20T18:44:45Z",
  "published" : "2026-08-20T18:44:45Z",
  "aliases" : [ ],
  "summary" : "Winter: My Account preview exposes another backend user's profile by record ID",
  "details" : "### Impact\n\n`Backend\\Controllers\\MyAccount`, introduced in v1.2.13, declares an empty `$requiredPermissions` array so that any authenticated backend user can manage their own account. It implements the `FormController` behavior, which exposes three routable actions — `create`, `update` and `preview` — that each take a record id from the URL.\n\n`index()` passes the authenticated user's own id to the behavior, but the inherited actions were left routable and `formFindModelObject()` was not scoped, so a caller-supplied id resolved against an unscoped `Backend\\Models\\User` query:\n\n```\nGET /backend/backend/myaccount/preview/{other_user_id}\n```\n\n`preview` disclosed the target user's first name, last name, login, email address and avatar; `update` was equally routable and additionally disclosed role, group membership, superuser flag and throttle state. Password controls render a mask, so no credential material was exposed. Backend user ids are sequential and trivially enumerated, and as these are `GET` actions no CSRF token is involved.\n\nThe behavior's AJAX handlers (`create_onSave`, `update_onSave`, `update_onDelete`) were also dispatchable on these routes, but cross-user writes were blocked by the `Backend\\Models\\User` authorization guards added in v1.2.13. The confirmed impact is unauthorized disclosure of backend user profile data.\n\nTo actively exploit this security issue, an attacker would need access to the Backend with a user account with any level of access.\n\n### Patches\n\n`MyAccount` no longer exposes the generic record actions it never used as routes, and its form lookup is now pinned to the authenticated user:\n\n- `protected $guarded = ['create', 'update', 'preview'];` removes the inherited actions from routing. The guard has to be at the routing layer, as handler dispatch (`{action}_{handler}`) runs before the page action.\n- `formExtendQuery()` constrains every lookup made by the behavior to the current user's key.\n\nThis security issue has been fixed as of **v1.2.14** (commit [`cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb`](https://github.com/wintercms/winter/commit/cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb)).\n\n### Workarounds\n\nThere is no supported workaround other than upgrading. If you cannot upgrade immediately, you may apply the fix manually in `modules/backend/controllers/MyAccount.php`:\n\n1. Add `protected $guarded = ['create', 'update', 'preview'];` to the controller.\n2. Add a `formExtendQuery()` method that scopes the lookup to the current user:\n\n```php\npublic function formExtendQuery(\\Winter\\Storm\\Database\\Builder $query): void\n{\n    $query->whereKey($this->user->getKey());\n}\n```\n\n### References\n\n- https://github.com/wintercms/winter/security/advisories/GHSA-j5jq-cr68-v2xx\n- https://github.com/wintercms/winter/commit/cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb\n\n\nCredit to Awwader ([@NRAwwad](https://github.com/NRAwwad)) for reporting the issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Email us at [hello@wintercms.com](mailto:hello@wintercms.com)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "winter/wn-backend-module"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.2.13"
      }, {
        "fixed" : "1.2.14"
      } ]
    } ],
    "versions" : [ "1.2.13" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/security/advisories/GHSA-mpmw-f6h6-3g26"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/commit/cdbc8f5a23db27f72ccec658a8e5769e6d9f6dcb"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/wintercms/winter"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/wintercms/winter/releases/tag/v1.2.14"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-20T18:44:45Z",
    "nvd_published_at" : null
  }
}