VulnerabilityPublished 9 Aug 2024Updated 3 Nov 2025

CVE-2024-36460: Zabbix · Plaintext Storage of a Password

Affects ZabbixSource GCVE Database

Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 30 Oct 2026, 02:18 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (Zabbix)	CVSS 3.1	8.1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Zabbix Zabbix	Affected 0 – 7.0.0alpha1 5 affected builds	Fixed in–

AI-suggested

Until an official fix is available, restrict access to the front-end audit log to trusted users only and monitor audit log access closely to prevent unauthorized viewing of plaintext passwords.

Description

CVE-2024-36460 is a vulnerability in Zabbix where the front-end audit log displays passwords in unprotected plaintext. This exposure allows users with access to the audit log to view sensitive password information without encryption or masking. The issue affects multiple versions of Zabbix including 5, 0, 6.0.0, 6.4.0, and 7.0.0alpha1. The vulnerability has a high severity rating with a CVSS score of 8.1, indicating a significant confidentiality impact. No official patch or remediation details are provided in the available data.

Impact

The vulnerability allows unauthorized disclosure of plaintext passwords through the front-end audit log, compromising confidentiality and integrity of credentials. This can lead to unauthorized access if attackers or unauthorized users gain audit log access. The high CVSS score reflects the critical nature of password exposure, which can facilitate further attacks or privilege escalation within affected Zabbix deployments.

Summary

The vulnerability identified as CVE-2024-36460 in Zabbix involves plaintext storage and display of passwords within the front-end audit log. This flaw corresponds to CWE-256, which concerns the storage of sensitive information in plaintext. The audit log feature exposes unprotected passwords, allowing anyone with audit log access to see these passwords in clear text. The vulnerability affects several specified versions of Zabbix, including 5, 0, 6.0.0, 6.4.0, and 7.0.0alpha1. The CVSS 3.1 base score is 8.1, reflecting network attack vector, low attack complexity, required privileges, no user interaction, and high confidentiality and integrity impact but no availability impact. There is no indication of known exploits in the wild or vendor-provided patches at this time.

CWE-256Plaintext Storage of a Password (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores a password in plaintext within resources such as memory or files.
Architecture and Design
Avoid storing passwords in easily accessible locations.
Architecture and Design
Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
A programmer might attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password because the encoding can be detected and decoded easily.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.7.5 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 02:18 UTC

WeaknessesCWE-256

Technical details

References

Community reviews

Related threats