AzuraCast/AzuraCast vulnerable to cross-site scripting

Exploitation

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

CVSS

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

EPSS

• CVE-2023-2191: 0.50% estimated exploitation activity in the next 30 days; percentile 43.16 (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.

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).

Published by the source

20 Apr 2023, 03:30 UTC

Last modified by the source

7 Nov 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q55c-hmpf-6h2g

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

# Patch Next advisory brief: CVE-2023-2191

Advisory: AzuraCast/AzuraCast vulnerable to cross-site scripting
IDs: CVE-2023-2191, GHSA-q55c-hmpf-6h2g
Record: https://patchnext.com/advisories/cve-2023-2191 (revision 1, source checked 26 Oct 2026, 14:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: azuracast/azuracast 0.18.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist azuracast/azuracast: affected < 0.18.0; fixed in 0.18.0

## Suggested inspection (read-only)
- Packagist azuracast/azuracast: 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 azuracast/azuracast.
- 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-q55c-hmpf-6h2g (GitHub-reviewed advisory GHSA-q55c-hmpf-6h2g lists affected ranges: Packagist azuracast/azuracast >=0 <0.18.0)

Commands are suggestions: review each one before running it.