AzuraCast has Path Traversal in currentDirectory Parameter that Enables Remote Code Execution via Media Upload

Exploitation

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

CVSS

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

EPSS

• CVE-2026-42605: 0.83% estimated exploitation activity in the next 30 days; percentile 57.65 (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.

Summary The currentDirectory request parameter in the Flow.js media upload endpoint (POST /api/station/{stationid}/files/upload) is not sanitized for path traversal sequences. When combined with a local filesystem storage backend (the default), an authenticated user with media management permissions can write arbitrary files outside the station's media storage directory, achieving remote code execution by writing a PHP webshell to the web root. Details In backend/src/Controller/Api/Stations/Files/FlowUploadAction.php, the currentDirectory parameter is read directly from user input at line 79 and prepended to the sanitized filename at line 83: While $flowResponse-getClientFullPath() is sanitized via UploadedFile::filterClientPath() (which strips .. segments), the $currentDir value is prepended after this sanitization, reintroducing traversal capability. This $destPath is passed to MediaProcessor::processAndUpload() at line 95-98. The critical issue is in the finally block at…

Published by the source

4 May 2026, 21:16 UTC

Last modified by the source

13 May 2026, 13:42 UTC

Source last checked

26 Oct 2026, 14:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vp2f-cqqp-478j

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

# Patch Next advisory brief: CVE-2026-42605

Advisory: AzuraCast has Path Traversal in `currentDirectory` Parameter that Enables Remote Code Execution via Media Upload
IDs: CVE-2026-42605, GHSA-vp2f-cqqp-478j
Record: https://patchnext.com/advisories/cve-2026-42605 (revision 1, source checked 26 Oct 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
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-vp2f-cqqp-478j (GitHub-reviewed advisory GHSA-vp2f-cqqp-478j lists affected ranges: Packagist azuracast/azuracast >=0 <=0.23.5)

Commands are suggestions: review each one before running it.