How severe is CVE-2026-22254?

CVE-2026-22254 has a CVSS score of 0/10, rated NONE. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-22254?

CVE-2026-22254 affects the following packages: winter/wn-cms-module (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-22254?

Update winter/wn-cms-module to 1.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22254 is resolved across your whole dependency graph.

How do I detect CVE-2026-22254 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for winter/wn-cms-module, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-22254 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2026-22254 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-22254 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-22254?

CVE-2026-22254 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-22254?

CVE-2026-22254 is classified as Cross-site Scripting (XSS) (CWE-79), CWE-80 (CWE-80). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-22254 published, and has it been updated?

CVE-2026-22254 was published on February 6, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

NONE severity

CVE-2026-22254 — wn-cms-module

NONEFix: wintercms/winter@8a7f74b

CVE-2026-22254 is a none-severity (CVSS 0) Cross-site Scripting (XSS) vulnerability in winter/wn-cms-module. A fix is available for winter/wn-cms-module — see the affected versions and patch details below.

Winter Affected by Stored Cross-Site Scripting (XSS) in Asset Manager

Also known asGHSA-m7gw-rffq-rxjm

Published

Feb 6, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22254.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘winter/wn-cms-module

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Affected versions of Winter CMS allow users with access to the CMS Asset Manager were able to upload SVGs without automatic sanitization.

To actively exploit this security issue, an attacker would need access to the Backend with a user account with the following permission: cms.manage_assets

The Winter CMS maintainers strongly recommend that the cms.manage_assets permission only be reserved to trusted administrators and developers in general.

Patches

Sanitization of SVG assets is now applied automatically when uploading through the CMS Asset Manager.

This security issue has been fixed as of https://github.com/wintercms/winter/commit/8a7f74b004fcd19721764fc63af0cdb339d9fb65.

Workarounds

If users cannot upgrade, they may apply commit https://github.com/wintercms/winter/commit/8a7f74b004fcd19721764fc63af0cdb339d9fb65 to their Winter CMS installation manually to resolve this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`winter/wn-cms-module`	all versions	1.2.10`composer require winter/wn-cms-module:^1.2.10`

Affected Products

1 product · 1 configurations

Application

winterwintercms

< 1.2.10

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for winter/wn-cms-module, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update winter/wn-cms-module to 1.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22254 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

## Impact Affected versions of Winter CMS allow users with access to the CMS Asset Manager were able to upload SVGs without automatic sanitization. To actively exploit this security issue, an attacker would need access to the Backend with a user account with the following permission: `cms.manage_assets` The Winter CMS maintainers strongly recommend that the `cms.manage_assets` permission only be reserved to trusted administrators and developers in general. ## Patches Sanitization of SVG assets is now applied automatically when uploading through the CMS Asset Manager. This security issue ha