dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-46496

CRITICAL · 9.3 CVSS v4.0 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable

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 · unedited
HAX CMS helps manage microsite universe with PHP or NodeJs backends. A stored cross-site scripting (XSS) vulnerability exists in versions prior to 26.0.0 due to improper sanitization of the `<video-player>` component. The component allows `javascript:` URIs in the `source` attribute, which are executed when the page is viewed. This enables attackers to execute arbitrary JavaScript in the context of the victim’s browser and access sensitive data such as JWT tokens and more. Version 26.0.0 fixes the issue.

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 confidence

HAX CMS versions prior to 26.0.0 contain a stored cross-site scripting (XSS) vulnerability in the `<video-player>` component. The component fails to sanitize the `source` attribute, allowing `javascript:` URIs to be stored and executed when victims view affected pages. This enables arbitrary JavaScript execution in the victim's browser context, exposing sensitive data such as JWT tokens.

MitigationUpgrade HAX CMS to version 26.0.0 or later, which implements proper sanitization of the video-player component's source attribute to reject javascript: URIs.

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
Low
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify HAX CMS installation and version
    Locate the HAX CMS installation directory and check the package.json, version file, or admin dashboard for the installed version number. Compare against the affected range (prior to 26.0.0).
    Affected if Installed version is below 26.0.0
  2. Check for video-player component usage
    Search the CMS content database or content files for instances of the <video-player> HTML element. This can be done by querying the database or searching file contents for 'video-player' tags.
    Affected if The <video-player> component is present in any stored content pages
  3. Inspect video-player source attributes
    Examine the source attribute values in all <video-player> elements found in the database or content files. Look for the attribute syntax: source="..." and inspect what URI scheme is used.
    Affected if Any source attribute contains a javascript: URI scheme
  4. Verify content authoring permissions
    Determine which user roles have permission to create or edit content containing the video-player component. Check role-based access control settings in the CMS admin panel.
    Affected if Users with content creation access include untrusted or anonymous users
  5. Check for existing XSS exploitation indicators
    Review browser console logs, server access logs, and CMS audit logs for patterns indicating XSS exploitation, such as requests containing 'javascript:' in URL parameters or referrer headers with executed payloads.
    Affected if Logs show execution of javascript: URIs or unexpected script behavior in user sessions

You are affected if running HAX CMS version below 26.0.0 AND the video-player component is in use, with any source attributes containing javascript: URIs indicating active exploitation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HAX CMS to version 26.0.0 or later, which implements proper sanitization of the video-player component's source attribute to reject javascript: URIs.

Recommended fix High confidence

26.0.0

  1. Backup the current HAX CMS installation and database before upgrading
  2. Review the release notes for version 26.0.0 to understand any configuration or migration requirements
  3. Upgrade HAX CMS to version 26.0.0 using the appropriate package manager or installation method (npm for NodeJS or composer for PHP)
  4. Clear any cached content to ensure the new version is fully applied
  5. Verify the fix by attempting to use a javascript: URI in a <video-player> component source attribute and confirming it is blocked/sanitized
  6. Test that legitimate video playback functionality still works correctly after the upgrade
Caveat Review release notes for any breaking changes between your current version and 26.0.0, as minor version jumps may include configuration or API changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46496 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46496 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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