CVE-2026-56347
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAVideo TopMenu plugin through version 26.0 contains a stored cross-site scripting vulnerability in menu item rendering due to missing output encoding of icon classes, URLs, and text labels. Attackers can inject malicious JavaScript through unescaped menu item fields that execute for all site visitors, potentially stealing session cookies or performing unauthorized actions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe AVideo TopMenu plugin through version 26.0 suffers from a stored cross-site scripting vulnerability where menu item fields (icon classes, URLs, and text labels) are rendered without proper output encoding, allowing injected JavaScript to persist and execute for all site visitors.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm AVideo platform installationLocate the AVideo web application files. Check for index.php or the main AVideo directory structure on the web server.Affected if AVideo platform is not installed
-
Identify TopMenu plugin versionNavigate to the plugin directory (usually in plugin/TopMenu or similar). Check plugin.json, plugin.info, or a version file within the TopMenu plugin folder. Compare the version number to 26.0.Affected if TopMenu plugin version is 26.0 or lower
-
Verify TopMenu plugin is enabledAccess the AVideo admin panel. Navigate to the plugins or extensions management section. Check if TopMenu is listed as active/enabled.Affected if TopMenu plugin is enabled
-
Check for configured menu itemsAccess the TopMenu plugin settings in the admin panel. Look for menu item configuration options where icon classes, URLs, and text labels can be defined.Affected if Menu items have been created or configured in the plugin
-
Inspect rendered menu HTML for encodingVisit the site frontend. Right-click and inspect the rendered TopMenu HTML. Examine the icon class (i.e., class attribute), URL (href attribute), and text label (between tags) for any unencoded special characters like <, >, ", or '.Affected if Menu item fields contain unencoded HTML/JavaScript characters when rendered
A user is affected if the AVideo platform has the TopMenu plugin enabled with version 26.0 or lower and menu items exist that contain unescaped HTML or script content in their icon, URL, or text fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply output encoding (HTML entity escaping) to all menu item fields before rendering. Implement input validation and consider Content Security Policy headers as defense-in-depth.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56347 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data