CVE-2023-29452
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 · uneditedCurrently, geomap configuration (Administration -> General -> Geographical maps) allows using HTML in the field “Attribution text” when selected “Other” Tile provider.
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 confidenceThe GLPI geomap configuration allows HTML injection in the 'Attribution text' field when 'Other' Tile provider is selected. This unsanitized input is rendered on geographical map pages, creating a stored Cross-Site Scripting (XSS) vulnerability where malicious JavaScript can execute in the browsers of users viewing the maps.
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>= 6.0.0, <= 6.0.17= 6.4.0= 6.4.1CVSS 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.
-
Check Zabbix versionAccess the Zabbix web interface, go to Administration > Users > Media types, or use the API endpoint /api/infos to retrieve the Zabbix server version. Alternatively, check the Zabbix frontend footer which displays the version.Affected if The installed version is 6.0.0 through 6.0.17, or exactly 6.4.0 or 6.4.1.
-
Verify geomap feature is in useIn the Zabbix web interface, navigate to Monitoring > Maps or check if any maps are configured that utilize the geomap functionality. This feature is typically used for geographical visualization of hosts.Affected if Geomap maps or widgets have been created and are accessible to users.
-
Check Tile provider configurationEdit an existing geomap map or create a new one. In the map or widget configuration, locate the Tile provider setting. Look for whether 'Other' is selected as the Tile provider.Affected if The 'Other' Tile provider option is selected in any geomap configuration.
-
Inspect Attribution text fieldWhile in the geomap Tile provider configuration with 'Other' selected, examine the 'Attribution text' field. Look for any HTML tags, script elements, or JavaScript event handlers present in this field.Affected if The Attribution text field contains raw HTML such as <script>, <img>, <iframe>, or JavaScript event handlers like onclick, onerror, or similar.
-
Verify if map is accessible to usersCheck the permissions and sharing settings of the geomap to confirm which users or user groups can view the map where the Attribution text is rendered.Affected if The geomap with the malicious Attribution text is accessible to users other than the administrator who entered the content.
A user is affected if they have Zabbix version 6.0.0-6.0.17, 6.4.0, or 6.4.1, with a geomap configured using the 'Other' Tile provider that displays unsanitized HTML in the Attribution text field and that map is accessible to 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 HTML sanitization or output encoding when rendering the Attribution text field to strip or escape scriptable HTML tags, or disable HTML rendering entirely in this field.
Zabbix 6.0.18+ or 6.4.2+ (or migrate to latest stable 6.4 LTS/7.0)
- 1. Back up your current Zabbix configuration and database
- 2. Plan maintenance window for the upgrade process
- 3. Download Zabbix version 6.0.18 or later, or version 6.4.2 or later from the official Zabbix download page
- 4. Follow the standard Zabbix upgrade procedure for your installation method (packages, source, or appliance)
- 5. After upgrade, verify the Geographical maps settings (Administration -> General -> Geographical maps) no longer accept HTML in the Attribution text field
- 6. Test that the geomap functionality works correctly with tile providers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29452 — 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-29452 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