LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27568: AVideo has Stored Cross-Site Scripting via Markdown Comment Injection

WWBN AVideo is an open source video platform. Prior to version 21.0, 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. 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. Version 21.0 contains a fix. As a workaround, validate and block unsafe URI schemes (e.g., `javascript:`) before rendering Markdown, and enable Parsedown Safe Mode.

MediumCVSS 5.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-27568 affects WWBN AVideo before 21.0. A logged-in, low-privilege user can place a persistent malicious Markdown link in a video comment. If another user clicks it, JavaScript can run in that user’s browser. Business risk is highest where AVideo is internet-facing, comments are enabled, and administrators review user comments while logged in.

Executive priority

Treat as a scheduled but prompt remediation for affected AVideo sites. Prioritize internet-facing or community-facing platforms, and environments where administrators regularly interact with user comments. The issue has a vendor fix in 21.0 and no provided evidence of active exploitation, but the potential impact to privileged sessions makes delay undesirable.

Technical view

AVideo before 21.0 renders Markdown comments using Parsedown 1.7.4 without Safe Mode. Markdown links are not sufficiently sanitized, allowing unsafe URI schemes such as javascript: to be rendered as clickable links. This is stored XSS, CWE-79, with CVSS 4.0 score 5.1. The advisory states possible impacts include session hijacking, privilege escalation including admin takeover, and data exfiltration after user interaction.

Likely exposure

Exposure is limited to organizations running WWBN AVideo versions earlier than 21.0, especially with authenticated users able to comment on videos. The attacker needs a low-privilege account, and exploitation requires a victim to click the malicious rendered link. Public exploitation is not indicated by the provided sources, and the CVE is not listed as KEV in the bundle.

Exploitation context

This is not a drive-by unauthenticated server takeover. It is a persistent client-side attack path: an authenticated attacker posts a malicious comment, and a victim must interact with the link. The risk increases if administrators or privileged users click user-submitted comment links while logged in, because their browser session may be abused.

Researcher notes

The root issue is unsafe Markdown link rendering in comments due to Parsedown without Safe Mode and insufficient URI scheme filtering. Validation should focus on affected version, comment capability, Markdown handling, and presence of the 21.0 fix. Avoid assuming broader product impact beyond WWBN AVideo versions before 21.0, as the provided sources do not support that.

Mitigation direction

  • Upgrade WWBN AVideo to version 21.0 or later.
  • If immediate upgrade is not possible, enable Parsedown Safe Mode where applicable.
  • Validate and block unsafe URI schemes before rendering Markdown.
  • Limit who can post comments until remediation is complete.
  • Advise administrators not to click links in user-submitted comments before remediation.

Validation and detection

  • Inventory AVideo deployments and identify versions earlier than 21.0.
  • Confirm whether video comments and Markdown rendering are enabled.
  • Review vendor advisory GHSA-rcqw-6466-3mv7 for current guidance.
  • Verify the installed code includes the referenced fix commit or release 21.0.
  • Check logs and content moderation queues for suspicious comment links.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27568 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.1 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.1CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.1Medium
CVSS 4.0 vector shape for CVE-2026-27568Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WWBNAVideo< 21.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.