CVE-2023-32721
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 · uneditedA stored XSS has been found in the Zabbix web application in the Maps element if a URL field is set with spaces before URL.
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 confidenceA stored XSS vulnerability exists in Zabbix's web interface where malicious JavaScript can be injected through the URL field in Maps elements when spaces precede the URL. The application fails to properly sanitize or validate the input, allowing stored scripts to execute when the map is viewed by other users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.0.0, <= 4.0.47>= 5.0.0, <= 5.0.36>= 6.0.0, <= 6.0.20>= 6.4.0, <= 6.4.5= 7.0.0CVSS 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
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Zabbix versionAccess the Zabbix web interface and check the version (typically visible in the footer of the login page or in the 'System information' section under Administration > Scripts or by querying the API endpoint or checking the frontend version file)Affected if The installed version falls within 4.0.0-4.0.47, 5.0.0-5.0.36, 6.0.0-6.0.20, 6.4.0-6.4.5, or 7.0.0
-
Verify Maps feature is in useNavigate to Monitoring > Maps in the Zabbix web interface and confirm if any custom maps have been createdAffected if Custom maps exist in the Zabbix instance
-
Inspect Map element URL fields for leading whitespaceEdit each map and examine the URL field within map elements (right-click elements > Edit > URL field) for any URLs that begin with one or more space charactersAffected if Any Map element contains a URL value that starts with one or more whitespace characters
-
Check map viewing access by other usersVerify permissions configuration for the maps (Monitoring > Maps > Edit > Sharing) to determine if other users or user groups can view the mapsAffected if Maps with suspicious URLs are accessible to users other than the map creator
-
Review recent map activity logsCheck the Audit log (Reports > Audit) for entries related to Map element creation or modification to identify recent changes to URL fieldsAffected if There are audit log entries showing Map element URL modifications that may have introduced leading whitespace
A user is affected if they run a vulnerable Zabbix version and have Maps configured with elements whose URL fields contain leading whitespace, particularly if those maps are viewable by multiple users.
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.
dbcve · scopedImplement proper input validation and output encoding for the URL field in Zabbix Maps to strip or properly escape leading whitespace and special characters before storing and rendering the data.
Upgrade to the latest stable release in your major version branch (4.0.48+, 5.0.37+, 6.0.21+, or 6.4.6+) or migrate to Zabbix 6.4/7.0 LTS
- 1. Back up your current Zabbix database and configuration files before proceeding with any upgrade.
- 2. Identify your current Zabbix version by checking the Zabbix web interface footer or using the zabbix_server -V command.
- 3. For Zabbix 4.0.x users: Upgrade to Zabbix 4.0.48 or later (or migrate to a supported branch like 5.0 or 6.0).
- 4. For Zabbix 5.0.x users: Upgrade to Zabbix 5.0.37 or later (or migrate to 6.0/6.4 LTS).
- 5. For Zabbix 6.0.x users: Upgrade to Zabbix 6.0.21 or later.
- 6. For Zabbix 6.4.x users: Upgrade to Zabbix 6.4.6 or later.
- 7. After upgrade, clear browser cache and verify the Maps functionality works correctly with URLs containing spaces.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32721 — 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-2023-32721 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