CVE-2026-61575: AVideo-Encoder vulnerable to stored DOM cross-site scripting through queue titles

Published Oct 28, 2026
·
Updated

AVideo is a video-sharing Platform. Prior to 8.1.0, view/queue.php uses pathinfo on the caller-controlled fileURI and stores its filename through setTitle in encoderqueue.title without neutralization. fileURI is not in the objects/security.php filter lists, and the Login::canUpload() capability needed to submit a queue entry can be self-granted using an attacker-controlled login site without legitimate encoder credentials. view/index.php loads queue.json from view/queue.json.php into the #grid jQuery Bootgrid table; its title formatter concatenates row.title into raw cell HTML. An attacker can therefore store an HTML title whose event handler runs in a privileged viewer's browser. Encoder::getAll limits nonadministrators to their own streamer's rows, so the victim must be an administrator who sees all rows or an operator on the attacker's streamer. A second .html() sink in the progress panel uses the same title but additionally depends on a helper script loaded from the streamer; the Bootgrid sink is reachable from encoder code alone. The script can read session-visible data and rendered streamer credentials, act with the viewer's privileges, and execute again for each qualifying viewer until the row is removed. This issue is fixed in version 8.1.0.

Affected Software

1 affected component
AVideo AVideo-Encoder<8.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade AVideo-Encoder to a version that resolves this vulnerability.

    Fixed in 8.1.0

Event History

Oct 28, 2026
CVE Published
via MITRE·09:57 PM
Data Sourced
via MITRE·09:57 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which users are exposed to the stored script when viewing the queue?

The primary Bootgrid sink affects administrators, who can see all queue rows, and operators viewing rows for the attacker's streamer. Nonadministrators are limited to rows from their own streamer.

2

What does an attacker need to submit a malicious queue title?

The attacker needs to submit a queue entry with a controlled fileURI whose filename becomes the stored title. Although queue submission requires Login::canUpload(), the capability can be self-granted through an attacker-controlled login site without legitimate encoder credentials.

3

Does exploitation require a streamer-hosted helper script?

No. The queue table's Bootgrid title formatter is reachable from encoder code alone. A separate progress-panel sink also uses the title, but that path additionally requires a helper script loaded from the streamer.

4

What could the injected script do in a privileged viewer's browser?

It can read session-visible data and rendered streamer credentials, and act with the privileges of the viewer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203