dbcve.org
Zabbix ServerApplication · Zabbix

CVE-2023-32725

HIGH · 8.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to after 6.4.6 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 website configured in the URL widget will receive a session cookie when testing or executing scheduled reports. The received session cookie can then be used to access the frontend as the particular user.

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

The URL widget in the affected application leaks session cookies to configured external websites when users test or execute scheduled reports. An attacker who controls or monitors the target URL can capture these session cookies and use them to authenticate to the application frontend as the victim user, achieving session hijacking.

MitigationRestrict the URL widget to internal/trusted domains only, implement SameSite=Strict or SameSite=Lax attributes on session cookies, or disable cookie transmission to external URLs entirely.

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
Zabbix ServerApplication
Affected:>= 6.0.0, <= 6.0.21>= 6.4.0, <= 6.4.6= 7.0.0
FrontendApplication
Affected:>= 6.0.0, <= 6.0.21>= 6.4.0, <= 6.4.6= 7.0.0

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 Server version
    Access the Zabbix UI, navigate to Administration > System Information, and note the Server version. Alternatively, use the Zabbix API endpoint apiinfo.version or check the server version file in the Zabbix installation directory.
    Affected if The installed version falls within 6.0.0-6.0.21, 6.4.0-6.4.6, or equals 7.0.0
  2. Check Zabbix Frontend version
    Access the Zabbix UI, navigate to Administration > System Information, and note the Frontend version. Alternatively, check the frontend version file in the web server directory where Zabbix is installed.
    Affected if The installed version falls within 6.0.0-6.0.21, 6.4.0-6.4.6, or equals 7.0.0 and differs from the server version
  3. Identify URL widgets in dashboards
    In the Zabbix UI, navigate to Monitoring > Dashboards and review each dashboard for URL widgets. Click on each URL widget to inspect its configured URL target.
    Affected if Any URL widget is configured pointing to an external or untrusted domain outside your organization
  4. Check scheduled reports for URL actions
    Navigate to Reports > Scheduled reports and review each report configuration to see if any include URL widget actions or links to external URLs.
    Affected if Any scheduled report is configured to access external URLs that could receive session cookies during execution

Your environment is affected if you run any Zabbix Server or Frontend version within the affected ranges AND have URL widgets configured pointing to external domains or scheduled reports that trigger external URL access.

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 a release after 6.4.6
Interim mitigation

Restrict the URL widget to internal/trusted domains only, implement SameSite=Strict or SameSite=Lax attributes on session cookies, or disable cookie transmission to external URLs entirely.

Recommended fix Moderate confidence

Zabbix 6.0.22+, 6.4.7+, or 7.0.1+ (Server and Frontend)

  1. 1. Identify which Zabbix Server and Frontend versions are currently deployed in your environment.
  2. 2. For Zabbix 6.0.x deployments: Upgrade to Zabbix Server 6.0.22 or later, and ensure Frontend is also upgraded to 6.0.22 or later.
  3. 3. For Zabbix 6.4.x deployments: Upgrade to Zabbix Server 6.4.7 or later, and ensure Frontend is also upgraded to 6.4.7 or later.
  4. 4. For Zabbix 7.0.0 deployments: Upgrade to Zabbix Server 7.0.1 or later, and ensure Frontend is also upgraded to 7.0.1 or later.
  5. 5. After upgrading, verify the Zabbix services are running correctly and the frontend is accessible.
  6. 6. Test the URL widget functionality to confirm the fix is working as expected.
  7. 7. Review user session handling and consider rotating sessions if any suspicious activity was observed.
Caveat Review Zabbix release notes for your target version to check for any breaking changes or required migration steps before upgrading

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

Fix this in Zabbix Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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