Is CVE-2026-116139 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-116139 being exploited in the wild.

How severe is CVE-2026-116139?

Medium severity, with a CVSS score of 5.4, published 25 October 2026.

Which products and versions are affected?

WWBN AVideo 26.0 through 29.3.0.

How is CVE-2026-116139 attacked?

It is attacked over the network.

Am I affected by CVE-2026-116139?

Check whether you run WWBN AVideo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-116139: WWBN AVideo stored cross-site scripting in comments

CVE-2026-116139 · Severity: medium · CVSS 5.4 · Published 2026-10-25

WWBN AVideo is a video streaming platform that allows users to comment on videos. Authenticated users can inject malicious JavaScript into video comments through improperly sanitized HTML, which then executes in other users' browsers when they view the comments. This could allow attackers to steal session data or perform actions on behalf of victims.

Technologies: WWBN AVideo. Vendors: WWBN.

Quick answers

Is CVE-2026-116139 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116139 being exploited in the wild.
How severe is CVE-2026-116139?: Medium severity, with a CVSS score of 5.4, published 25 October 2026.
Which products and versions are affected?: WWBN AVideo 26.0 through 29.3.0.
Is there a fix for CVE-2026-116139?: No fixed version is recorded yet. Disable comment submission and display for untrusted content, or apply a strict HTML allowlist at the final rendering boundary that removes event attributes and unsafe URI schemes. A restrictive Content Security Policy can provide defense in depth until a patch is available. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-116139 attacked?: It is attacked over the network.
Am I affected by CVE-2026-116139?: Check whether you run WWBN AVideo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Disable comment submission and display for untrusted content, or apply a strict HTML allowlist at the final rendering boundary that removes event attributes and unsafe URI schemes. A restrictive Content Security Policy can provide defense in depth until a patch is available.

Technical details

A stored XSS vulnerability exists in the markDownToHTML() function, which processes comment Markdown and fails to sanitize event-handler attributes when an HTML image tag appears at the start of a block. The vulnerable code path disables Parsedown's safe mode and delegates leading img/a tags to raw HTML handling without the inline sanitizer protections. An authenticated commenter can bypass sanitization by posting a comment like "<img src=x onerror=alert(1)>", which executes in victims' browsers under the application origin when the comment is viewed.

Affected products

WWBN AVideo 26.0 through 29.3.0

Timeline

2026-10-08: disclosed
2026-10-25: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.