Authenticated script execution via unescaped display name
Published Apr 20, 2023 · Updated Feb 5, 2025
Stored XSS in AzuraCast before 0.18.0 allows remote authenticated users to execute JavaScript through a crafted display name. The header-menu template renders getDisplayName() without HTML escaping, so stored markup becomes executable page content. An existing account can plant the payload, but data exposure requires a higher-privileged administrator to use Log In As on that account.
Summary
What happened
Stored XSS in AzuraCast before 0.18.0 allows remote authenticated users to execute JavaScript through a crafted display name. The header-menu template renders getDisplayName() without HTML escaping, so stored markup becomes executable page content. An existing account can plant the payload, but data exposure requires a higher-privileged administrator to use Log In As on that account.
The record
- CVE
- CVE-2023-2191
- Published
- Apr 20, 2023
- Updated
- Feb 5, 2025
- Vendor
- AzuraCast
- Product
- AzuraCast
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 20, 2023CVE publishedPublication date reported by the CVE source.
- Feb 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <0.18
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr bounty proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo