AzuraCast has Missing Permissions Check on Media File Download, Allowing Cross-Station Data Exfiltration

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The GET /api/station/{stationid}/file/{id}/play endpoint, handled by PlayAction, is missing the Middleware\Permissions check that protects all sibling routes in the same /file/{id} route group. Any authenticated user can download media files from any station, regardless of whether they have permissions on that station. In multi-tenant deployments, this enables cross-station media exfiltration. Details In backend/config/routes/apistation.php, the /file/{id} route group (lines 407-429) defines four endpoints: The middleware chain for the /play endpoint is: GetStation → RequireStation → RequireLogin → StationSupportsFeature(Media) → PlayAction. The RequireLogin middleware (backend/src/Middleware/RequireLogin.php) only verifies a valid session/API key exists — it does not check station-level permissions. The controller at backend/src/Controller/Api/Stations/Files/PlayAction.php:84 calls $this-mediaRepo-requireForStation($id, $station), which verifies the media belongs to the…

Published by the source

4 May 2026, 21:19 UTC

Last modified by the source

4 May 2026, 21:19 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qff7-q5fm-8p76

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

# Patch Next advisory brief: GHSA-qff7-q5fm-8p76

Advisory: AzuraCast has Missing Permissions Check on Media File Download, Allowing Cross-Station Data Exfiltration
IDs: GHSA-qff7-q5fm-8p76
Record: https://patchnext.com/advisories/ghsa-qff7-q5fm-8p76 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.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.23.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist azuracast/azuracast: affected <= 0.23.5; fixed in 0.23.6

## 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-qff7-q5fm-8p76 (GitHub-reviewed advisory GHSA-qff7-q5fm-8p76 lists affected ranges: Packagist azuracast/azuracast >=0 <=0.23.5)

Commands are suggestions: review each one before running it.