How many CVEs have patched myaccount_onSave?

1 published CVEs changed myaccount_onSave in wintercms/winter, in 1 distinct patches totalling 26 changed lines, between 2026 and 2026.

What is the latest CVE that changed myaccount_onSave?

CVE-2026-35445 (Winter: Authenticated backend users can bypass Users controller permission checks), published 2026-08-26, changed lines 175 to 179 of modules/backend/controllers/Users.php.

How does myaccount_onSave compare to the rest of wintercms/winter?

wintercms/winter has 15 CVEs with a located fix in total; 1 of them changed myaccount_onSave.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

wintercms/winter

Function

myaccount_onSave

Name: myaccount_onSave in wintercms/winter: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

modules/backend/controllers/Users.php

Last patched August 26, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

26

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

myaccount_onSave in wintercms/winter was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 26 lines in total.

wintercms/winter has 15 CVEs with a located fix in total, so 7% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed myaccount_onSave, newest first, with the lines each fix touched.

Winter: Authenticated backend users can bypass Users controller permission checks
CVE-2026-35445 · lines 175–179 · +2 −24
High · CVSS 7.1
EPSS 0.4%2026-08-26

Get an alert when the next CVE fix lands in wintercms/winter, with the patched functions.

Monitor winter CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in wintercms/winter changed by the most CVE fixes.

onUpload2 CVEs · modules/cms/widgets/AssetList.php __construct2 CVEs · modules/system/twig/SecurityPolicy.php checkMethodAllowed2 CVEs · modules/system/twig/SecurityPolicy.php renderCss2 CVEs · modules/backend/models/EditorSetting.php renderCss2 CVEs · modules/backend/models/BrandSetting.php compileCss1 CVEs · modules/backend/models/EditorSetting.php

All patched functions in wintercms/winter

Frequently asked questions

Common questions about CVE fixes to myaccount_onSave.

How many CVEs have patched myaccount_onSave?: 1 published CVEs changed myaccount_onSave in wintercms/winter, in 1 distinct patches totalling 26 changed lines, between 2026 and 2026.
What is the latest CVE that changed myaccount_onSave?: CVE-2026-35445 (Winter: Authenticated backend users can bypass Users controller permission checks), published 2026-08-26, changed lines 175 to 179 of modules/backend/controllers/Users.php.
How does myaccount_onSave compare to the rest of wintercms/winter?: wintercms/winter has 15 CVEs with a located fix in total; 1 of them changed myaccount_onSave.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track wintercms/winter CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing