CVE-2026-23928
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 · uneditedThe Item history widget (in Zabbix 7.0+) or the Plain text widget (in Zabbix 6.0) can execute injected JavaScript when HTML display is enabled. This can allow an attacker to perform unauthorized actions depending on which user opens a dashboard containing these widgets. The malicious JavaScript would have to come from a monitored host controlled by the attacker. Note: the Item history widget is a replacement for the Plain text widget since Zabbix 7.0.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in Zabbix where the Item history widget (v7.0+) or Plain text widget (v6.0) executes injected JavaScript when HTML display is enabled. Attackers inject malicious JavaScript via data from compromised monitored hosts, which then executes in the browser sessions of users viewing dashboards containing these widgets.
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Zabbix versionQuery the Zabbix server for its version via the web interface (Administration > System information) or by checking the Zabbix package/version file on the server. Compare the version number against the affected ranges: v7.0+ or v6.0.Affected if The installed version is Zabbix v7.0 or later, or Zabbix v6.0.
-
Identify Item history widgets with HTML enabledIn the Zabbix web interface, navigate to Monitoring > Dashboards. Review each dashboard for Item history widgets. For each widget, open its configuration and inspect the 'HTML output' or 'Display as HTML' setting. Check if it is set to enabled or checked.Affected if A dashboard contains an Item history widget (Zabbix v7.0+) with HTML rendering enabled.
-
Identify Plain text widgets with HTML enabledIn the Zabbix web interface, navigate to Monitoring > Dashboards. Review each dashboard for Plain text widgets. For each widget, open its configuration and inspect the 'HTML output' or 'Display as HTML' setting. Check if it is set to enabled or checked.Affected if A dashboard contains a Plain text widget (Zabbix v6.0) with HTML rendering enabled.
-
Review data sources from monitored hostsExamine the data being received from monitored hosts that feed into the affected widgets. Verify whether any host data contains unsanitized input that could contain script tags or HTML injection vectors.Affected if Compromised or untrusted monitored hosts are feeding data into widgets with HTML enabled.
You are affected if running Zabbix v7.0+ or v6.0 and any dashboard contains an Item history or Plain text widget with HTML rendering enabled fed by potentially untrusted monitored host data.
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 dataDisable HTML rendering in the Item history or Plain text widget configurations, or upgrade to a patched Zabbix version once available.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23928 — 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-23928 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