What is CVE-2023-37611?

CVE-2023-37611 is a medium-severity cross-site scripting (XSS) vulnerability in neos/media-browser (composer), affecting versions < 7.3.19. It is fixed in 7.3.19, 8.0.16, 8.1.11, 8.2.11, 8.3.9. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2023-37611?

CVE-2023-37611 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of neos/media-browser are affected by CVE-2023-37611?

neos/media-browser (composer) versions < 7.3.19 is affected.

Is there a fix for CVE-2023-37611?

Yes. CVE-2023-37611 is fixed in 7.3.19, 8.0.16, 8.1.11, 8.2.11, 8.3.9. Upgrade to this version or later.

Is CVE-2023-37611 exploitable, and should I be worried?

Whether CVE-2023-37611 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-37611 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-37611 in neos/media-browser

Q: How severe is CVE-2023-37611?

CVE-2023-37611 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of neos/media-browser are affected by CVE-2023-37611?

neos/media-browser (composer) versions < 7.3.19 is affected.

Q: Is there a fix for CVE-2023-37611?

Yes. CVE-2023-37611 is fixed in 7.3.19, 8.0.16, 8.1.11, 8.2.11, 8.3.9. Upgrade to this version or later.

Q: Is CVE-2023-37611 exploitable, and should I be worried?

Whether CVE-2023-37611 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-37611 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-37611?

Upgrade: neos/media-browser to 7.3.19 or later, neos/media-browser to 8.0.16 or later, neos/media-browser to 8.1.11 or later, neos/media-browser to 8.2.11 or later, neos/media-browser to 8.3.9 or later.

Summary

Neos CMS Cross Site Scripting vulnerability

Cross Site Scripting (XSS) vulnerability in Neos CMS 8.3.3 allows a remote authenticated attacker to execute arbitrary code via a crafted SVG file uploaded to the neos/management/media component. To make use of this attack vector, the attacker must either be able to upload a maliciously crafted file or coerce someone with the needed access to upload said file to Neos. Even if such a file is uploaded and subsequently delivered, it is possible to use CSP to protect against attacks being executed from such a file.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2023-37611 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.3.19, 8.0.16, 8.1.11, 8.2.11, 8.3.9); upgrading removes the vulnerable code path.

Affected versions

neos/media-browser (< 7.3.19) neos/media-browser (>= 8.0.0, < 8.0.16) neos/media-browser (>= 8.1.0, < 8.1.11) neos/media-browser (>= 8.2.0, < 8.2.11) neos/media-browser (>= 8.3.0, < 8.3.9)

Security releases

neos/media-browser → 7.3.19 (composer) neos/media-browser → 8.0.16 (composer) neos/media-browser → 8.1.11 (composer) neos/media-browser → 8.2.11 (composer) neos/media-browser → 8.3.9 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

neos/media-browser to 7.3.19 or later; neos/media-browser to 8.0.16 or later; neos/media-browser to 8.1.11 or later; neos/media-browser to 8.2.11 or later; neos/media-browser to 8.3.9 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-37611? CVE-2023-37611 is a medium-severity cross-site scripting (XSS) vulnerability in neos/media-browser (composer), affecting versions < 7.3.19. It is fixed in 7.3.19, 8.0.16, 8.1.11, 8.2.11, 8.3.9. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2023-37611? CVE-2023-37611 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of neos/media-browser are affected by CVE-2023-37611? neos/media-browser (composer) versions < 7.3.19 is affected.
Is there a fix for CVE-2023-37611? Yes. CVE-2023-37611 is fixed in 7.3.19, 8.0.16, 8.1.11, 8.2.11, 8.3.9. Upgrade to this version or later.
Is CVE-2023-37611 exploitable, and should I be worried? Whether CVE-2023-37611 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-37611 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-37611?
- Upgrade neos/media-browser to 7.3.19 or later
- Upgrade neos/media-browser to 8.0.16 or later
- Upgrade neos/media-browser to 8.1.11 or later
- Upgrade neos/media-browser to 8.2.11 or later
- Upgrade neos/media-browser to 8.3.9 or later