Summary
Vulnerability Type
Stored Cross-Site Scripting (XSS), CWE-79.
Affected Product/Versions
AVideo 18.0.
Root Cause Summary
AVideo allows Markdown in video comments and uses Parsedown (v1.7.4) without Safe Mode enabled. Markdown links are not sufficiently sanitized, allowing javascript: URIs to be rendered as clickable links.
Impact Summary
An authenticated low-privilege attacker can post a malicious comment that injects persistent JavaScript. When another user clicks the link, the attacker can perform actions such as session hijacking, privilege escalation (including admin takeover), and data exfiltration.
Resolution/Fix
The issue was confirmed and fixed in the master branch. An official release will be published soon.
Workarounds
Until the release is available, validate and block unsafe URI schemes (e.g., javascript:) before rendering Markdown, and enable Parsedown Safe Mode.
Credits/Acknowledgement
Reported by Arkadiusz Marta (https://github.com/arkmarta/).
Impact
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-27568? CVE-2026-27568 is a medium-severity cross-site scripting (XSS) vulnerability in wwbn/avideo (composer), affecting versions < 21.0. It is fixed in 21.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of wwbn/avideo are affected by CVE-2026-27568? wwbn/avideo (composer) versions < 21.0 is affected.
- Is there a fix for CVE-2026-27568? Yes. CVE-2026-27568 is fixed in 21.0. Upgrade to this version or later.
- Is CVE-2026-27568 exploitable, and should I be worried? Whether CVE-2026-27568 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-27568 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-27568? Upgrade
wwbn/avideoto 21.0 or later.