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

CVE-2026-46511

HIGH · 8.7 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 →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click

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. Prior to version 26.0.0, an attack chain utilizing Stored XSS alongside dynamic token exposure in the `/system/api/connectionSettings` endpoint allows an authenticated attacker to perform a complete cross-tenant account takeover. The API dynamically leaks the active session's authentication tokens (including the `jwt`, `user_token`, `site_token`, and `appstore_token`) into a global JavaScript variable (`window.appSettings`). An attacker can exploit the XSS vulnerability to force a victim's browser to silently fetch their specific connection settings, extract the tokens, and exfiltrate them to an attacker-controlled webhook. Version 26.0.0 patches 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

This is a chained vulnerability in HAX CMS where an authenticated attacker combines Stored XSS with insecure token exposure. The /system/api/connectionSettings endpoint dynamically leaks authentication tokens (jwt, user_token, site_token, appstore_token) into the client-side window.appSettings JavaScript variable, enabling cross-tenant account takeover via token exfiltration.

MitigationUpgrade to version 26.0.0 which patches the token exposure. Additionally, implement Content Security Policy and input validation to mitigate the XSS vector used in this attack chain.

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
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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 and determine the installed version number. Common locations include the admin dashboard, package.json, or the footer of the CMS interface. Compare your version to 26.0.0 which is the patched version.
    Affected if Installed version is lower than 26.0.0 and the application uses JWT or token-based authentication.
  2. Verify /system/api/connectionSettings endpoint accessibility
    Attempt to access the /system/api/connectionSettings endpoint via HTTP GET request, either with authentication or without to test exposure. Inspect the HTTP response headers and body.
    Affected if The endpoint returns a 200 OK response and contains any authentication-related data in the response body.
  3. Inspect response for token leakage in window.appSettings
    Examine the raw response from /system/api/connectionSettings. Search the response body for the string 'window.appSettings' and check if it contains any of these tokens: jwt, user_token, site_token, appstore_token.
    Affected if The response contains window.appSettings with any of the token fields (jwt, user_token, site_token, or appstore_token) populated with actual values.
  4. Check for Stored XSS vulnerability
    If the application has user input functionality (such as content editing, comments, or metadata fields), attempt to inject a benign script tag into a stored field. Verify if the input is reflected in the page without proper sanitization.
    Affected if User-supplied HTML or JavaScript content is stored and rendered without sanitization or encoding, allowing script execution.

Your environment is affected if HAX CMS version is below 26.0.0 AND the /system/api/connectionSettings endpoint exposes authentication tokens in window.appSettings, particularly when combined with an exploitable Stored XSS vector.

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 to version 26.0.0 which patches the token exposure. Additionally, implement Content Security Policy and input validation to mitigate the XSS vector used in this attack chain.

Recommended fix High confidence

HAX CMS version 26.0.0 or later

  1. 1. Identify the current installed version of HAX CMS by checking the package.json, composer.json, or the admin interface.
  2. 2. If the current version is prior to 26.0.0, plan for upgrade to version 26.0.0 or later.
  3. 3. Create a complete backup of the HAX CMS database, codebase, and configuration files.
  4. 4. For Node.js backend: Run `npm update` or `npm install haxcms@latest` to upgrade to the latest version.
  5. 5. For PHP backend: Update the composer.json to require version ^26.0.0 and run `composer update`.
  6. 6. After upgrading, clear any cached files and regenerate static assets if applicable.
  7. 7. Verify the upgrade was successful by checking the version number in the admin interface.
  8. 8. Test critical functionality including authentication and the `/system/api/connectionSettings` endpoint to confirm tokens are no longer exposed to `window.appSettings`.
Caveat None explicitly mentioned in the advisory; upgrade is recommended to address the security vulnerability

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46511 — 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-46511 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