CVE-2026-116545 · Package
NO FIX YET
The All-in-One Video Gallery WordPress plugin up to and including 5.0.0 does not sanitize a custom field label for subtitle tracks. An authenticated subscriber can store a script that runs in the browser of any visitor who opens the affected page.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the All-in-One Video Gallery plugin at version 5.0.0 or earlier with the Player Library option set to Plyr/Vidstack. Exposure needs a logged-in subscriber-level account, so sites with open registration or untrusted contributors are the most exposed. Sites on the Video.js default or without the plugin can skip it.
Not affected if no-untrusted-subscribers, plugin-not-installed, videojs-default-player
Who cares all-in-one-video-gallery, wordpress, wordpress-plugin
5.0.0 or lower in the WordPress plugins screen.aiovg_player_settings[player]; the flaw applies only when it is vidstack (Plyr/Vidstack) rather than the Video.js default.No fix yet, per the sources.
The All-in-One Video Gallery – Video Player & Galleries for YouTube, Vimeo & Self-Hosted Videos plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'custom_fields[].value.label (for key='track')' parameter in all versions up to, and including, 5.0.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the site's Player Library option to be configured as Plyr/Vidstack (aiovg_player_settings[player]='vidstack') rather than the Video.js default, as the DOM innerHTML sink exists only in the Plyr/Vidstack template path.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.