Skip to main content
CVE-2026-116545VulnerabilityPublished

The All-in-One Video Gallery – Video Player & Galleries for YouTube, Vimeo & Self-Hosted Videos plugin for WordPress

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116545· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium · patch available : update All-in-One Video Gallery (WordPress plugin) when convenient.

Data as of 6 Nov 2026, 13:24 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.4
Patch
Available
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
plugins360All-in-One Video Gallery – Video Player & Galleries for YouTube, Vimeo & Self-Hosted VideosAffected
  • <=5.0.0
Fixed in–

AI-suggested

Since the vulnerability depends on the Player Library setting, administrators can mitigate risk by reverting to the default Video.js player instead of Plyr/Vidstack. Additionally, restricting subscriber privileges or reviewing input sanitization measures may reduce exposure. Monitor the vendor advisory for official fixes or updates.

Description

The All-in-One Video Gallery WordPress plugin up to version 5.0.0 is vulnerable to stored DOM-based cross-site scripting (XSS) via the 'custom_fields[].value.label' parameter when the Player Library is set to Plyr/Vidstack. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. This vulnerability arises from insufficient input sanitization and output escaping in the Plyr/Vidstack template path.

References

Community reviews

Loading reviews…