WINTER/WN-BACKEND-MODULE · CVE-2026-126061 · Package
FIX → 1.2.14
Winter CMS's My Account backend page lets any logged-in backend user open another backend user's profile by changing the record ID in the URL. The exposed data includes names, login, email and avatar, and the update view also shows role, group, superuser flag and throttle state.
first public Aug 19, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running Winter CMS backend version 1.2.13 that have backend user accounts with any level of access. The exposure needs a logged-in backend account; anonymous visitors and the public frontend are not affected. Sites on 1.2.12 or earlier do not have the MyAccount controller, and sites already on 1.2.14 are fixed.
Not affected if auth-required, frontend-only, version-below-1.2.13
Who cares php, self-hosted, winter-cms
wn-backend-module version in composer.lock or with composer show winter/wn-backend-module; affected is 1.2.13.protected $guarded in modules/backend/controllers/MyAccount.php; its absence on an affected version means the flaw is present.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; 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 actions no CSRF token is involved.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 1.2.14
winter/wn-backend-module to 1.2.14updateGETThe 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.
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).
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:
protected $guarded = ['create', 'update', 'preview']; to the controller.formExtendQuery() method that scopes the lookup to the current user:public function formExtendQuery(\Winter\Storm\Database\Builder $query): void
{
$query->whereKey($this->user->getKey());
}
Credit to Awwader (@NRAwwad) for reporting the issue.
If you have any questions or comments about this advisory:
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.