Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain account with upload permission
-
DeliverySet malicious trailer1 URL payload
-
ExploitStore XSS in YouPHPFlix2 template/playlist
-
ExecutionVictim views affected video page
-
PersistPayload breaks out of onclick/iframe src
-
ImpactExecute JavaScript in victim's session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Attacker must hold an authenticated AVideo account that has video upload permission (PR:L) and must set a malicious value in the video's trailer1 field. Exploitation also requires victim interaction (UI:P): a user must view a page that renders trailer1 - specifically the YouPHPFlix2 templates (BigVideo.php, BigVideoButtons.php, row_info.php) or channel playlists (channelPlaylistItems.php). The payload works against default rendering because, pre-patch, these templates emitted trailer1 directly into an onclick='flixFullScreen(...)' / avideoModalIframe(...) string or an iframe src attribute with no HTML escaping and only an !empty() check. Limiting factors: requires a valid upload-capable account, requires a victim to load the attacker-influenced content, and impact is realized in the victim's browser context rather than directly on the server; affects AVideo through 29.2.0. |
| Impact | This is a genuinely notable but not top-tier-urgent issue. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/SC:H/SI:H) scores 9.3, but that score is inflated by treating the XSS as high-impact to both the vulnerable and subsequent systems. The two mitigating realities are PR:L (the attacker must already hold a legitimate account with upload permission) and UI:P (a victim must view the affected video page, channel playlist, or template), so this is not a remote-unauthenticated drive-by. There is no CISA KEV listing and no public exploit code was provided in the intelligence, so exploitation status is 'no public exploit identified at time of analysis' - note that discovery/reporting by VulnCheck is a credibility signal but is distinct from active exploitation. No EPSS score was supplied, so widespread-exploitation probability cannot be quantified from this data. The source-code diff strongly CONFIRMS the vulnerability is real and well-understood: unescaped trailer1 values flowed into onclick strings and iframe src attributes across four templates, fixed via isValidURL() plus htmlspecialchars(ENT_QUOTES). Net: a credible, patch-available stored XSS best treated as a medium-to-high remediation priority for AVideo operators that allow multiple uploaders, rather than an emergency internet-wide threat. One caveat: the vendor rates confidentiality/integrity impact High (account/session compromise of admins who view attacker content), which is plausible for stored XSS reaching privileged viewers but should be weighed against the authenticated, interaction-dependent precondition. |
| Exploit ScenarioDerived | An attacker who holds a low-privilege account with video upload permission sets a crafted trailer1 URL containing quote/angle-bracket breakout payloads. When another user - potentially an administrator or channel owner - browses the video, channel playlist, or YouPHPFlix2 template, the unescaped value breaks out of the onclick handler or iframe src and runs attacker JavaScript in their session. No public exploit code was identified, but the mechanism is fully confirmed by the vendor patch diff. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 04, 2026
Stored cross-site scripting in WWBN AVideo through 29.2.0 allows an authenticated user who holds video upload permission to store a crafted trailer1 URL that is later rendered without escaping in the YouPHPFlix2 templates (BigVideo.php, BigVideoButtons.php, row_info.php) and in the channel playlist view (channelPlaylistItems.php). The injected value can break out of an onclick='flixFullScreen(...)' / avideoModalIframe(...) JavaScript string or an iframe src attribute, so any visitor who loads an affected page has attacker-controlled JavaScript executed in their browser context. Exploitation requires both a valid upload-capable account (PR:L) and victim interaction with a rendering page (UI:P), and the security impact is realized in the victim's browser rather than directly on the server; no public exploit code or CISA KEV entry was identified at time of analysis, and the vendor advisory and fix commit are already public.
RemediationAI
Vendor-released fix available as upstream commit c4adfde13d1f18e3a415722471efdcd8ab480035 (referenced from advisory GHSA-6wfr-c7fw-4xvw), which replaces the !empty() guard with isValidURL() validation and applies htmlspecialchars(..., ENT_QUOTES, 'UTF-8') at every trailer1 sink in plugin/YouPHPFlix2/view/BigVideo.php, BigVideoButtons.php, row_info.php and view/channelPlaylistItems.php; no individually numbered patched release was confirmed in the provided data, so site operators should upgrade to the first AVideo release that contains this commit or apply the commit directly and then re-run the bundled regression test tests/Security/SecurityHardeningRegressionTest.php to confirm all four sinks validate and escape. If immediate upgrading is not possible, the practical compensating controls are to strip or disable the trailer1 feature (for example by removing or overriding the trailer1 field handling in the admin video-edit form so the stored value can never be attacker-controlled), or to disable the YouPHPFlix2 plugin and the channel-playlist trailer button entirely - acknowledging that this removes trailer playback functionality for legitimate users. Because the injection point is only reachable by accounts with upload permission, tightening upload rights (restricting upload permission to trusted roles, requiring moderation of new uploads before publication, and auditing existing video records for trailer1 values containing quotes, angle brackets, HTML entities, or non-http(s) schemes such as javascript:) provides meaningful interim risk reduction but does not fix the underlying missing output encoding. A WAF rule that blocks quote/angle-bracket/script patterns in trailer1 submissions is a partial, bypassable mitigation and should not be treated as a substitute for the code fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a CWE-79 stored cross-site scripting issue arising from an incomplete earlier fix (GHSA-v7vx-v9q9-qhw3). The root cause is double: setTrailer1() validates the trailer1 field only with FILTER_VALIDATE_URL, which still accepts raw single and double quotes, angle brackets, HTML entities, and javascript: URIs; and the templates that display trailer1 escaped nothing, guarding output only with an !empty() check. Because the value is concatenated into a JavaScript string context - onclick="flixFullScreen('<trailer1>', '')" in plugin/YouPHPFlix2/view/BigVideoButtons.php and row_info.php, and onclick="avideoModalIframe('<trailer1>')" in view/channelPlaylistItems.php - a quote in the payload terminates the string and lets an attacker append arbitrary script. In plugin/YouPHPFlix2/view/BigVideo.php the same unescaped value is written directly into an iframe src attribute, permitting attribute breakout. The upstream fix combines isValidURL() validation at each sink (replacing the weaker !empty() check) with htmlspecialchars(..., ENT_QUOTES, 'UTF-8') HTML escaping of the parsed trailer URL, and a regression test (tests/Security/SecurityHardeningRegressionTest.php) asserts both the validation and the escaping are present at all four sinks; the fact that a dedicated regression test had to be added indicates the project is treating this as a follow-up to a previous, insufficient trailer1 hardening.
Know when Avideo gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Authenticated uploader (PR:L) plants stored payload executed only when a victim views the page (UI:R); XSS crosses into the victim's browser context (S:C) with limited confidentiality/integrity impact and no availability effect.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
WWBN AVideo through 29.2.0 contains a stored cross-site scripting vulnerability that allows users with upload permission to inject script by setting a malicious video trailer1 URL. The value is rendered unescaped in YouPHPFlix2 templates and channel playlists, letting attackers break out of onclick strings or iframe src attributes to execute JavaScript in victims' browsers.
Technical POC Analysis
CWE-79: Improper Neutralization of Input During Web Page Generation.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
WWBN AVideo (up to version 29.2.0) contains a critical stored cross-site scripting vulnerability that allows authenticated users with upload permissions to inject malicious code that executes in the browsers of any visitor viewing affected pages. This puts the entire user base at risk of credential theft, session hijacking, and malware infection, and could damage the organization's reputation and lead to regulatory penalties. Immediate patching is required to protect users and maintain trust.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
A cross-site scripting (xss) vulnerability exists in the functiongetOpenGraph videoName functionality of WWBN AVideo 11.
An issue in WWBN AVideo v.12.4 through v.14.2 allows a remote attacker to execute arbitrary code via the systemRootPath
A directory traversal vulnerability exists in the unzipDirectory functionality of WWBN AVideo 11.6 and dev master commit
An insufficient entropy vulnerability exists in the salt generation functionality of WWBN AVideo dev master commit 15fed
Unauthenticated SQL injection in AVideo before 24.0.
OS injection vulnerability in World Wide Broadcast Network AVideo version before 12.4, allows attackers to execute arbit
A reflected cross-site scripting (xss) vulnerability exists in the charts tab selection functionality of WWBN AVideo 11.
A cross-site scripting (xss) vulnerability exists in the channelBody.php user name functionality of WWBN AVideo 11.6 and
A cross-site scripting (xss) vulnerability exists in the videoAddNew functionality of WWBN AVideo 11.6 and dev master co
An insufficient entropy vulnerability exists in the userRecoverPass.php recoverPass generation functionality of WWBN AVi
WWBN AVideo is an open source video platform. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable
AVideo is an open source video platform. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low
EUVD-2026-92110
GHSA-m6h8-gp7c-3qmv
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB