AVideo has Stored XSS via Unescaped Menu Item Fields in TopMenu Plugin
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist wwbn/avideo
- Affected
- <= 26.0
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-gmpc-fxg2-vcmq lists affected ranges: Packagist wwbn/avideo >=0 <=26.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary The TopMenu plugin renders menu item fields (icon classes, URLs, and text labels) directly into HTML without applying htmlspecialchars() or any other output encoding. Since menu items are rendered on every public page through plugin hooks, a single malicious menu entry results in stored cross-site scripting that executes for every visitor to the site. An admin user who is tricked into saving a crafted menu item (or an attacker who gains admin access) can compromise all site visitors. Details Multiple output locations in the TopMenu plugin render user-controlled data without escaping: In HTMLMenuRight.php:24, the icon class is injected directly: In HTMLMenuRight.php:40, the URL is rendered without encoding: In HTMLMenuLeft.php:32, same pattern for the left menu: In index.php:49, the menu item text is echoed raw: Menu item data is saved via menuItemSave.json.php with no sanitization in the setter methods. The stored values are loaded from the database and rendered on every page…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-gmpc-fxg2-vcmq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-gmpc-fxg2-vcmq Advisory: AVideo has Stored XSS via Unescaped Menu Item Fields in TopMenu Plugin IDs: GHSA-gmpc-fxg2-vcmq Record: https://patchnext.com/advisories/ghsa-gmpc-fxg2-vcmq (revision 1, source checked 26 Oct 2026, 14:39 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist wwbn/avideo: affected <= 26.0 ## Suggested inspection (read-only) - Packagist wwbn/avideo: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on wwbn/avideo. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-gmpc-fxg2-vcmq (GitHub-reviewed advisory GHSA-gmpc-fxg2-vcmq lists affected ranges: Packagist wwbn/avideo >=0 <=26.0) Commands are suggestions: review each one before running it.
Loading voting…