AzuraCast: RCE via Liquidsoap string interpolation injection in station metadata and playlist URLs

Exploitation

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

CVSS

8.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary AzuraCast's ConfigWriter::cleanUpString() method fails to sanitize Liquidsoap string interpolation sequences (#{...}), allowing authenticated users with StationPermissions::Media or StationPermissions::Profile permissions to inject arbitrary Liquidsoap code into the generated configuration file. When the station is restarted and Liquidsoap parses the config, #{...} expressions are evaluated, enabling arbitrary command execution via Liquidsoap's process.run() function. Root Cause File: backend/src/Radio/Backend/Liquidsoap/ConfigWriter.php, line ~1345 This function only replaces " with ' and strips newlines. It does NOT filter: - #{...} — Liquidsoap string interpolation (evaluated as code inside double-quoted strings) - \ — Backslash escape character Liquidsoap, like Ruby, evaluates #{expression} inside double-quoted strings. process.run() in Liquidsoap executes shell commands. Injection Points All user-controllable fields that pass through cleanUpString() and are embedded in…

Published by the source

9 Mar 2026, 19:55 UTC

Last modified by the source

9 Mar 2026, 19:55 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-93fx-5qgc-wr38

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

# Patch Next advisory brief: GHSA-93fx-5qgc-wr38

Advisory: AzuraCast: RCE via Liquidsoap string interpolation injection in station metadata and playlist URLs
IDs: GHSA-93fx-5qgc-wr38
Record: https://patchnext.com/advisories/ghsa-93fx-5qgc-wr38 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
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.23.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist azuracast/azuracast: affected <= 0.23.3; fixed in 0.23.4

## 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-93fx-5qgc-wr38 (GitHub-reviewed advisory GHSA-93fx-5qgc-wr38 lists affected ranges: Packagist azuracast/azuracast >=0 <=0.23.3)

Commands are suggestions: review each one before running it.