dbcve.org
ZabbixApplication

CVE-2024-45699

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-02
Fix available
A fix is available. Upgrade to 6.0.37 / 6.4.21 or later.
See remediation →
58/100
Remediation priority · Elevated
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
The endpoint /zabbix.php?action=export.valuemaps suffers from a Cross-Site Scripting vulnerability via the backurl parameter. This is caused by the reflection of user-supplied data without appropriate HTML escaping or output encoding. As a result, a JavaScript payload may be injected into the above endpoint causing it to be executed within the context of the victim's browser.

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

A reflected Cross-Site Scripting (XSS) vulnerability exists in Zabbix's /zabbix.php?action=export.valuemaps endpoint. The backurl parameter is reflected in the HTTP response without proper HTML escaping or output encoding, allowing an attacker to inject malicious JavaScript that executes in the victim's browser session.

MitigationImplement proper output encoding/HTML escaping on the backurl parameter before it is reflected in any HTTP response. Use context-appropriate encoding functions (e.g., htmlspecialchars with ENT_QUOTES for HTML attribute contexts) to neutralize script injection attempts.

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
ZabbixApplication
Affected:>= 6.0.0, < 6.0.37>= 6.4.0, < 6.4.21>= 7.0.0, < 7.0.7

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Zabbix version
    Access the Zabbix web frontend footer or check the version file (e.g., include/version.php or via API: GET /apiinfo/version). Compare the installed version against the affected ranges: 6.0.0 to 6.0.36, 6.4.0 to 6.4.20, or 7.0.0 to 7.0.6.
    Affected if The installed version falls within any of the affected ranges (6.0.0-6.0.36, 6.4.0-6.4.20, or 7.0.0-7.0.6).
  2. Verify web frontend is accessible
    Confirm the Zabbix web interface is reachable at the expected hostname/IP (e.g., curl -I https://<zabbix-host>/zabbix.php).
    Affected if The Zabbix web frontend is accessible over HTTP/HTTPS.
  3. Confirm export.valuemaps endpoint exists
    Attempt to access the vulnerable endpoint with a test parameter: GET /zabbix.php?action=export.valuemaps&backurl=test
    Affected if The endpoint responds (even with an error), indicating the endpoint is active.
  4. Inspect backurl parameter reflection
    Send a request with a crafted backurl parameter (e.g., /zabbix.php?action=export.valuemaps&backurl=%3Cscript%3Ealert(1)%3C/script%3E) and examine the HTTP response body to see if the raw parameter value is reflected without encoding.
    Affected if The backurl parameter value appears unescaped in the response (e.g., literal <script> tags or unencoded quotes).

The environment is affected if Zabbix web frontend version falls within 6.0.0-6.0.36, 6.4.0-6.4.20, or 7.0.0-7.0.6 AND the /zabbix.php?action=export.valuemaps endpoint is accessible with the backurl parameter reflected without HTML escaping.

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
Upgrade available Upgrade to 6.0.37 / 6.4.21 / 7.0.7 or later
Fixed in 6.0.376.4.217.0.7
Interim mitigation

Implement proper output encoding/HTML escaping on the backurl parameter before it is reflected in any HTTP response. Use context-appropriate encoding functions (e.g., htmlspecialchars with ENT_QUOTES for HTML attribute contexts) to neutralize script injection attempts.

Recommended fix High confidence

6.0.37, 6.4.21, or 7.0.7 (or latest stable 7.0.x)

  1. Determine your current Zabbix installation version by checking the Zabbix interface or using 'zabbix_server -V'
  2. Identify which branch (6.0.x, 6.4.x, or 7.0.x) your current installation belongs to
  3. For Zabbix 6.0.x users: Upgrade to version 6.0.37 or later
  4. For Zabbix 6.4.x users: Upgrade to version 6.4.21 or later
  5. For Zabbix 7.0.x users: Upgrade to version 7.0.7 or later
  6. Alternatively, upgrade to the latest stable Zabbix release (7.0.x recommended for new deployments)
  7. After upgrade, verify the fix by checking that the /zabbix.php?action=export.valuemaps endpoint properly encodes the backurl parameter
Caveat Minor: Review Zabbix release notes for your target version to check for any behavioral changes between your current and target version

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

Fix this in Zabbix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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