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

CVE-2026-23926

HIGH · 7.3 CVSS v4.0 Published 2026-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
An authenticated (non-super) administrator can create a maintenance period with a JavaScript payload that is executed by any user that opens tooltip for that maintenance period in the Host navigator widget. This can allow the attacker to perform unauthorized actions depending on which user opens the tooltip.

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 · moderate confidence

This is a stored Cross-Site Scripting (XSS) vulnerability where an authenticated non-super administrator can inject malicious JavaScript into a maintenance period description. When other users view the tooltip for that maintenance period in the Host navigator widget, the injected script executes in their browser session, potentially allowing unauthorized actions.

MitigationImplement proper output encoding and context-aware escaping when rendering tooltip content in the Host navigator widget. Additionally, add input validation to restrict the types of content that can be included in maintenance period descriptions.

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

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/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 if maintenance period configuration is accessible
    Locate the maintenance period settings in your application admin panel or configuration area. This is typically found under system administration, scheduling, or maintenance settings where administrators define maintenance windows.
    Affected if Your environment allows authenticated users to create or modify maintenance period descriptions.
  2. Determine if Host navigator widget is enabled
    Check whether the Host navigator widget is present and active in your environment. This widget typically displays host/server information in a navigation panel and may show maintenance period tooltips.
    Affected if The Host navigator widget is enabled and visible to users in your deployment.
  3. Review maintenance period descriptions for injected content
    Access the maintenance period configuration and inspect all existing maintenance period entries. Examine the description fields for any unexpected characters, tags, or script elements such as <script>, javascript:, onload, onerror, or other XSS vectors.
    Affected if Any maintenance period description contains HTML, JavaScript, or encoded script content that was not intentionally added by an administrator.
  4. Verify tooltip rendering behavior
    If maintenance periods exist, trigger the display of the Host navigator widget tooltip for a maintenance period. Inspect the rendered HTML in the tooltip area using browser developer tools to see if description content is rendered as plain text or executed as code.
    Affected if Maintenance period description content is rendered as executable HTML or JavaScript in the tooltip rather than being displayed as plain text.

Your environment is affected if the Host navigator widget displays maintenance period tooltips and those descriptions contain any injected script or HTML content that executes in user browsers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper output encoding and context-aware escaping when rendering tooltip content in the Host navigator widget. Additionally, add input validation to restrict the types of content that can be included in maintenance period descriptions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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