# CVE-2026-22254: Winter Affected by Stored Cross-Site Scripting (XSS) in Asset Manager

> Attackers with asset management permissions can upload malicious SVGs to execute scripts in other users' browsers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-m7gw-rffq-rxjm

## What is CVE-2026-22254?

CVE-2026-22254 is a cross-site scripting vulnerability in wintercms winter, published on 6 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Winter is a free, open-source content management system (CMS) based on the Laravel PHP framework. Versions of Winter CMS before 1.2.10 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. This vulnerability is fixed in 1.2.10.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-22254?

2 open source packages ship an affected version, including winter/wn-cms-module. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `winter/wn-cms-module` | Packagist | All versions | 1.2.10 |
| `winter/wn-cms-module` | Packagist | All versions | 1.2.10 |

Products: Wintercms Winter.

## How do I fix CVE-2026-22254?

Upgrade winter/wn-cms-module to 1.2.10 or later.

## Is CVE-2026-22254 being exploited?

There is no known exploitation of CVE-2026-22254 in the wild and no public exploit code.

## Other vulnerabilities in wintercms winter

- [CVE-2026-27591](https://insights.sbomify.com/CVE-2026-27591/): Winter: Privilege escalation by authenticated backend users (critical 10.0)
- [CVE-2024-54149](https://insights.sbomify.com/CVE-2024-54149/): Winter CMS Modules allows a sandbox bypass in Twig templates leading to data modification and deletion (high 8.5)
- [CVE-2022-39357](https://insights.sbomify.com/CVE-2022-39357/): Winter vulnerable to Prototype Pollution in Snowboard framework (high 8.1)
- [CVE-2024-29686](https://insights.sbomify.com/CVE-2024-29686/): Winter CMS Server-Side Template Injection (SSTI) vulnerability (high 7.2)
- [CVE-2023-52085](https://insights.sbomify.com/CVE-2023-52085/): Winter CMS Local File Inclusion through Server Side Template Injection (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22254 and fix it if it is affected.

What it is: CVE-2026-22254 is a cross-site scripting vulnerability in wintercms winter, published on 6 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22254 in the wild and no public exploit code.

Affected packages and fixed versions:
- winter/wn-cms-module (Packagist): affected all versions; fixed in 1.2.10
- winter/wn-cms-module (Packagist): affected all versions; fixed in 1.2.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22254/ (Markdown: https://insights.sbomify.com/CVE-2026-22254/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22254
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22254
- OSV: https://osv.dev/vulnerability/CVE-2026-22254

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22254/
Summaries are generated and may contain mistakes; the official description above is the record.