AzuraCast through 0.23.8 Config Injection via frontend_config.custom_config
Affects AzuraCast through 0.23.8 on Shoutcast2-type stations, for users with the Manage station profile permission but without Manage station broadcasting permission. CVSS rates it 8.7 (high). No fix is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts list no workaround. One way to limit exposure is to review which users hold the Manage station profile permission without the Manage station broadcasting permission, and to restrict that combination where possible.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
CVE-2026-121427 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects AzuraCast; no fixed version is listed yet.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
AzuraCast through 0.23.8 fails to remove frontend_config.custom_config in PUT /station/{id}/profile/edit for users lacking the Manage station broadcasting permission, and the stored JSON is written verbatim as key=value lines into the Shoutcast sc_serv.conf file. An authenticated user with only the Manage station profile permission can override adminpassword, password, and portbase, or inject arbitrary directives via newlines in keys, hijacking the station's Shoutcast frontend.
What to do
Workaround: The checked facts list no workaround. One way to limit exposure is to review which users hold the Manage station profile permission without the Manage station broadcasting permission, and to restrict that combination where possible.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- AzuraCast AzuraCast
through 0.23.8
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121427
Is CVE-2026-121427 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A user with the Manage station profile permission can override the Shoutcast admin password, password and port, or inject arbitrary directives into the Shoutcast configuration. This lets them take over the station's Shoutcast frontend.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-121427?
AzuraCast: through 0.23.8.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 0 through 0.23.8 are listed as affected. The bug requires a Shoutcast2-type station frontend and a user who has Manage station profile permission but lacks Manage station broadcasting permission. To check, compare your AzuraCast version with 0.23.8 and review each station's frontend type and its users' permissions.Source: github.com, vulncheck.com
How do I fix CVE-2026-121427?
The checked facts list no fixed version, so no upgrade target can be given. Check the AzuraCast advisory for a patched release before relying on any version.Source: github.com, vulncheck.com
What if there's no patch?
The checked facts list no workaround. One way to limit exposure is to review which users hold the Manage station profile permission without the Manage station broadcasting permission, and to restrict that combination where possible.Source: github.com, vulncheck.com
Why do the sources disagree?
The description presents this as an authenticated issue, requiring a logged-in user with station permissions. The vector string lists PR:N, which means no privileges are required. The sources do not agree on whether a login is needed.Source: github.com, vulncheck.com