CVE-2023-2191

AzuraCast/AzuraCast prior to version 0.18.0 is vulnerable to stored cross-site scripting. An issue was identified where a user who already had an AzuraCast account could update their display name to inject malicious JavaScript into the header menu of the site. In a majority of cases, this menu is only visible to the current logged-in user (pages like the Administer Users page are unaffected by this vulnerability), but if a higher-privileged administrator uses the Log In As feature to masquerade as a user, then the JavaScript injection could exfiltrate certain data. Anonymous members of the public cannot exploit this vulnerability in an AzuraCast installation, so it is primarily of concern for multi-tenant installations (i.e. resellers).

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-2191 has a CVSS score of 3.5 (Low). The vector is network-reachable, high 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 (0.18.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2023-2191? CVE-2023-2191 is a low-severity cross-site scripting (XSS) vulnerability in azuracast/azuracast (composer), affecting versions < 0.18.0. It is fixed in 0.18.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2023-2191? CVE-2023-2191 has a CVSS score of 3.5 (Low). 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.
3. Which versions of azuracast/azuracast are affected by CVE-2023-2191? azuracast/azuracast (composer) versions < 0.18.0 is affected.
4. Is there a fix for CVE-2023-2191? Yes. CVE-2023-2191 is fixed in 0.18.0. Upgrade to this version or later.
5. Is CVE-2023-2191 exploitable, and should I be worried? Whether CVE-2023-2191 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
6. What actually determines whether CVE-2023-2191 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.
7. How do I fix CVE-2023-2191? Upgrade azuracast/azuracast to 0.18.0 or later.