CVE-2023-52083

mediumpriority · track · 19EPSS 0.003 · 24 %ileEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.31% (24th) EPSS
CVSS 4.8 · medium
Is it mine?
4 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-27

Winter is a free, open-source content management system. Prior to 1.2.4, users with the `media.manage_media` 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. This issue has been patched in v1.2.4.

01

cvss

Technical severity, 0–10. One row per scoring source.

4.8
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2–4.8

v3.14.8mediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:Nprimary · NVD / NIST USexploitability 1.7 · impact 2.7
v3.12lowCVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:Nsecondary · ENISA EU
v3.12lowCVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:Nsecondary · security-advisories@github.comexploitability 0.5 · impact 1.4
v3.12lowCVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:Nsecondary · OSV
v3.14.4mediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N/E:Usecondary · CVSS-BT (t0sche)
02

weaknesses

The CWE weakness classes this flaw belongs to.

03

affected products (4)

Products and version ranges known to be affected.

04

advisories (1)

Vendor and ecosystem advisories describing this.

  • GHSA-4wvw-75qh-fqjpWinter CMS Stored XSS through privileged upload of Media Manager file followed by renaming2023-12-28ghsa · osvUS

    ### Impact Users with the `media.manage_media` 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 potential harm of this vulnerability. That being said, all users are advised to update to the latest version (1.2.4) to ensure their systems remain secure. ### Patches This issue has been patched in v1.2.4. ### Workarounds Apply https://github.com/wintercms/winter/commit/2969daeea8dee64d292dbaa3778ea251e2a7e491 and https://github.com/wintercms/winter/commit/2969daeea8dee64d292dbaa3778ea251e2a7e491 manually if unable to upgrade to v1.2.4. ### References Related: https://github.com/wintercms/winter/security/advisories/GHSA-wjw2-4j7j-6gc3

05

also known as (3)

Other names and identifiers for this entity.

06

sources

Which sources assert this record, and when.

published 2023-12-28modified 2026-06-17
07

references (7)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan