dbcve.org
ZabbixApplication

CVE-2025-27240

HIGH · 7.2 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to 6.0.34 / 6.4.19 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
A Zabbix adminitrator can inject arbitrary SQL during the autoremoval of hosts by inserting malicious SQL in the 'Visible name' field.

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

SQL injection vulnerability in Zabbix allows authenticated administrators to execute arbitrary SQL commands by inserting malicious SQL in the 'Visible name' field during the host autoremoval process.

MitigationApply vendor-supplied security patch or upgrade to a fixed Zabbix version; implement input validation and parameterized queries for the 'Visible name' field.

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.34>= 6.4.0, < 6.4.19>= 7.0.0, < 7.0.4

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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. Identify Zabbix installation and version
    Check the Zabbix web interface footer for version number, or run 'zabbix_server --version' on the server, or query the package manager (dpkg -l zabbix-server or rpm -qi zabbix-server)
    Affected if Version is 6.0.0 through 6.0.33, 6.4.0 through 6.4.18, or 7.0.0 through 7.0.3
  2. Verify administrative access to Zabbix
    Confirm you have administrator-level access to the Zabbix web interface, as the vulnerability requires an authenticated administrator account
    Affected if You can access Zabbix with admin-level privileges enabling host configuration settings
  3. Locate host autoremoval configuration
    Navigate to Configuration > Hosts in the Zabbix web interface and look for autoremoval settings (typically under host configuration or maintenance settings), or check the 'host_removal' related database tables if you have database access
    Affected if The host autoremoval feature with a 'Visible name' field configuration exists and is accessible
  4. Check for exploitation indicators
    Review Zabbix server logs (/var/log/zabbix/zabbix_server.log) and database query logs for SQL syntax errors or anomalous SQL statements containing the Visible name field pattern, or inspect database table 'hosts' for unexpected SQL-like content in the 'name' field
    Affected if Suspicious SQL fragments appear in logs or the 'name' field contains unexpected SQL syntax

Your Zabbix instance is affected if it runs version 6.0.0-6.0.33, 6.4.0-6.4.18, or 7.0.0-7.0.3 and you have administrative access to configure host autoremoval with a Visible name field.

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.34 / 6.4.19 / 7.0.4 or later
Fixed in 6.0.346.4.197.0.4
Interim mitigation

Apply vendor-supplied security patch or upgrade to a fixed Zabbix version; implement input validation and parameterized queries for the 'Visible name' field.

Recommended fix High confidence

Upgrade to Zabbix 6.0.34 (for 6.0.x branch), 6.4.19 (for 6.4.x branch), or 7.0.4 (for 7.0.x branch)

  1. 1. Identify current Zabbix version by checking Administration > About in the Zabbix web interface, or running `zabbix_server --version` on the server
  2. 2. Determine which version branch is currently running (6.0.x, 6.4.x, or 7.0.x)
  3. 3. For Zabbix 6.0.x (versions 6.0.0 to 6.0.33): Upgrade to version 6.0.34 or later
  4. 4. For Zabbix 6.4.x (versions 6.4.0 to 6.4.18): Upgrade to version 6.4.19 or later
  5. 5. For Zabbix 7.0.x (versions 7.0.0 to 7.0.3): Upgrade to version 7.0.4 or later
  6. 6. Follow standard Zabbix upgrade procedure: stop Zabbix services, backup database, replace binaries, run database upgrade scripts, restart services
  7. 7. Verify the upgrade was successful and test core functionality
Caveat Minor version upgrades typically have minimal breaking changes; review Zabbix release notes for version-specific migration notes

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

Fix this in Zabbix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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