CVE-2026-105086 WWBN CVE debrief

Who should care

Defenders managing WWBN AVideo instances, especially those with untrusted users uploading content, should assess exposure and prioritize remediation. This includes reviewing the current deployment, identifying potential vulnerabilities, and implementing necessary security measures to prevent exploitation. Additionally, defenders should consider implementing compensating controls, such as monitoring and detection systems, to identify and respond topotential

Why it matters

This stored cross-site scripting vulnerability in WWBN AVideo allows authenticated uploaders to inject HTML, potentially leading to malicious script execution and compromise of user sessions or sensitive data. Defenders managing AVideo instances should assess exposure and prioritize remediation.

• Potential execution of malicious scripts in trending, gallery, embed, and playlist pages
• Possible compromise of user sessions or sensitive data
• Required verification of vulnerable AVideo instances
• Potential impact on the integrity of video content

Technical summary

The vulnerability exists due to the safeString() function stripping tags before decoding entities and running twice via setTitle() and save(). This allows attackers to store markup that executes in trending, gallery, embed, and playlist pages. The vulnerability is particularly concerning because it allows authenticated uploaders to inject HTML, potentially leading to malicious script execution and compromise of user sessions or sensitive data. Defenders managing AVideo instances should assess exposure and prioritize remediation.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in their environments, especially those with untrusted users uploading content.

Recommended defensive actions

• Verify and remediate vulnerable AVideo instances
• Restrict user input for video titles
• Implement additional security measures for untrusted user uploads
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability allows attackers to store markup that executes in trending, gallery, embed, and playlist pages due to the safeString() function stripping tags before decoding entities and running twice via setTitle() and save().

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.