GHSA-m7gw-rffq-rxjm is a none-severity (CVSS 0) Cross-site Scripting (XSS) vulnerability in winter/wn-cms-module. O3 Security confirms whether GHSA-m7gw-rffq-rxjm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Winter CMS has Stored Cross-site Scripting (XSS) in Asset Manager
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 GHSA-m7gw-rffq-rxjm.
Real-World Exposure
winter/wn-cms-moduleReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | winter/wn-cms-module | all versions | 1.2.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for winter/wn-cms-module. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-m7gw-rffq-rxjm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m7gw-rffq-rxjm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-m7gw-rffq-rxjm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m7gw-rffq-rxjm in your dependencies?
O3 detects GHSA-m7gw-rffq-rxjm across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.