Winter CMS Stored XSS through privileged upload of Media Manager file followed by renaming

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

2.0 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N

EPSS

• CVE-2023-52083: 0.31% estimated exploitation activity in the next 30 days; percentile 24.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Users with the media.managemedia permission can upload files to the Media Manager and rename them after uploading. Previously, media manager files were only sanitized on upload, not on renaming, which could have allowed a stored XSS attack. Although this was a security issue, it's important to note that its severity is low. To exploit the vulnerability, an attacker would already need to have trusted permissions in the Winter CMS backend. This means they would already have extensive access and control within the system. Additionally, to execute the XSS, the attacker would need to convince the victim to directly visit the URL of the maliciously uploaded SVG, and the application would have to be using local storage where uploaded files are served under the same domain as the application itself instead of a CDN. This is because all SVGs in Winter CMS are rendered through an img tag, which prevents any payloads from being executed directly. These two factors significantly limit the…

Published by the source

28 Dec 2023, 22:32 UTC

Last modified by the source

3 Jan 2024, 16:54 UTC

Source last checked

26 Oct 2026, 14:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4wvw-75qh-fqjp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-52083

Advisory: Winter CMS Stored XSS through privileged upload of Media Manager file followed by renaming
IDs: CVE-2023-52083, GHSA-4wvw-75qh-fqjp
Record: https://patchnext.com/advisories/cve-2023-52083 (revision 1, source checked 26 Oct 2026, 14:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: winter/wn-system-module 1.2.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist winter/wn-system-module: affected < 1.2.4; fixed in 1.2.4

## Suggested inspection (read-only)
- Packagist winter/wn-system-module: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on winter/wn-system-module.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4wvw-75qh-fqjp (GitHub-reviewed advisory GHSA-4wvw-75qh-fqjp lists affected ranges: Packagist winter/wn-system-module >=0 <1.2.4)

Commands are suggestions: review each one before running it.