Summary
A stored cross-site scripting vulnerability in AVideo's LiveLinks plugin allows scripts to be saved through live-link title and description fields without adequate sanitization. When visitors, including administrators, view the affected page, the stored script may execute within the site's origin.
Affected context
The issue occurs in AVideo deployments using the LiveLinks plugin when title or description values are accepted, stored, and later rendered without context-appropriate output encoding or sanitization. Exploitation risk is greater when a user with canStream permission can create or edit live-link content and privileged users regularly view the resulting page.
Exploit preconditions
- Attack surface: LiveLinks plugin title and description fields
- Required access: A user account with
canStreampermission or equivalent content-editing capability - Trigger point: A visitor's browser renders a live-link page containing the stored value
- Why exploitation is possible: User-controlled content is persisted and later inserted into an HTML response without sufficient sanitization or output encoding
Why this happens
The vulnerability results from treating user-controlled title and description values as trusted presentation content. Because the values are stored without adequate sanitization and rendered without context-aware encoding, browser script content can be interpreted as executable markup. This behavior maps to CWE-79: Improper Neutralization of Input During Web Page Generation, commonly known as cross-site scripting.
Potential impact
- Malicious scripts may execute in visitors' browsers within the site's origin
- Session information or accessible account data could be exposed
- Administrator actions could be performed through a victim's authenticated browser
- Content could be modified or misleading pages could be presented to users
- The vulnerability could support broader compromise if privileged browser sessions are targeted
General mitigation guidance
Mitigation generally centers on treating all submitted metadata as untrusted and applying context-appropriate output encoding at the point of rendering.
Common defensive patterns include:
- Sanitizing permitted markup with a narrowly defined allowlist, or rejecting markup when it is unnecessary
- Applying output encoding appropriate to the HTML, attribute, URL, or JavaScript context
- Validating input length, format, and character expectations without relying on validation as a substitute for encoding
- Enforcing authorization checks for creating and modifying live-link content
- Applying a restrictive Content Security Policy as defense in depth
- Limiting administrative exposure to user-generated content and using least-privilege accounts
How teams detect issues like this
Organizations can identify stored XSS risks through:
- Static analysis rules for unsafe HTML rendering, template interpolation, and direct DOM insertion
- Code review checks for missing output encoding in title, description, and other user-generated fields
- Dynamic testing that submits harmless browser-markup probes and verifies encoded rendering across affected pages
- Content-security and web-application firewall policies that flag unexpected script-bearing input
- Automated security review tools that trace user input from storage to HTML response sinks

