CVE-2025-67737: AzuraCast Vulnerable to Pre-Auth File Deletion & Admin RCE
An API endpoint that is intended for internal use by the SFTP software sftpgo was mistakenly exposed to the public-facing HTTP API for AzuraCast installations. This would allow a user with specific internal knowledge of a station's operations to craft a custom HTTP request that would affect the contents of a station's database, without revealing any internal information about the station.
Published Dec 11, 2025 · Updated Dec 12, 2025
Affected packages
azuracast/azuracast
- Ecosystem
- Composer (PHP)
- Affected
- <= 0.23.1
- Fixed in
- 0.23.2
- Check
composer show azuracast/azuracast
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
An API endpoint that is intended for internal use by the SFTP software sftpgo was mistakenly exposed to the public-facing HTTP API for AzuraCast installations.
This would allow a user with specific internal knowledge of a station's operations to craft a custom HTTP request that would affect the contents of a station's database, without revealing any internal information about the station.
With a request like:
curl -s -X POST "http://localhost/api/internal/sftp-event" -H "Content-Type: application/json" -d '{
"action": "pre-delete",
"username": "admin",
"path": "/var/azuracast/stations/test/media/test.mp3"
}'A remote user could simulate a request from sftpgo informing the software that a file was about to be deleted from the path given. In anticipation of this, AzuraCast would delete the corresponding database record for that file. While AzuraCast would then later discover on its own that the file actually exists and recreate the media record, it would not have the same playlist associations or custom metadata as the previous instance of the media record in the database.
Some mitigating factors affecting the severity of this issue include:
- A user would need to know a valid SFTP username corresponding to the specific station in question.
- A user would need to know the internal filesystem structure of a station (or be able to brute-force or guess paths).
- Any call to this internal API endpoint does not return any information to the calling process about what files are present or aren't, so no confidential internal information is revealed by this process.
Patched versions of AzuraCast specifically check that any calls to this internal URL are being called by the internal HTTP service, which only listens for activity on localhost and is not accessible from outside the container.
Credited to Cillian-Collins.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-42605
AzuraCast has Path Traversal in `currentDirectory` Parameter that Enables Remote Code Execution via Media Upload
high8.8May 4, 2026CVE-2026-42606
AzuraCast has Password Reset Poisoning via Untrusted X-Forwarded-Host Header that Leads to Account Takeover and 2FA Bypass
high8.1May 4, 2026GHSA-4fm3-ggg2-c6qx
AzuraCast's Missing RequireInternalConnection on Liquidsoap API Allows Low-Privilege Metadata Injection and Broadcast Disruption
medium6.3May 4, 2026GHSA-q4ph-8x8g-95f8
AzuraCast Vulnerable to Liquidsoap Code Injection via Incomplete cleanUpString-to-toRawString Migration in Remote Relay Password Field
high8.8May 4, 2026GHSA-qff7-q5fm-8p76
AzuraCast has Missing Permissions Check on Media File Download, Allowing Cross-Station Data Exfiltration
medium6.5May 4, 2026GHSA-93fx-5qgc-wr38
AzuraCast: RCE via Liquidsoap string interpolation injection in station metadata and playlist URLs
high8.7Mar 9, 2026
