CVE-2023-32723
CVE-2023-32723 is a high-severity vulnerability in Zabbix with a CVSS 3.x base score of 8.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-732.
Key facts
- Severity: High (CVSS 3.x base score 8.5)
- EPSS exploit prediction: 1% (43rd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-732
- Affected product: Zabbix
- Published:
- Last modified:
Description
Request to LDAP is sent before user permissions are checked.
Frequently asked questions
- What is CVE-2023-32723?
- Request to LDAP is sent before user permissions are checked.
- How severe is CVE-2023-32723?
- CVE-2023-32723 has a CVSS 3.x base score of 8.5, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability none.
- Is CVE-2023-32723 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2023-32723?
- CVE-2023-32723 primarily affects Zabbix. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2023-32723?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2023-32723 published?
- CVE-2023-32723 was published on 2023-10-12 and last updated on 2026-06-17.
References
- https://lists.debian.org/debian-lts-announce/2024/01/msg00012.html
- https://support.zabbix.com/browse/ZBX-23230
Affected products (4)
- cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
- cpe:2.3:a:zabbix:zabbix:4.0.19:rc1:*:*:*:*:*:*
- cpe:2.3:a:zabbix:zabbix:4.4.7:rc1:*:*:*:*:*:*
- cpe:2.3:a:zabbix:zabbix:5.0.0:alpha3:*:*:*:*:*:*
More vulnerabilities in Zabbix
- CVE-2007-0640 — Critical (CVSS 10.0): Buffer overflow in ZABBIX before 1.1.5 has unknown impact and attack vectors related to "SNMP IP addresses."
- CVE-2024-42327 — Critical (CVSS 9.9): A non-admin user account on the Zabbix frontend with the default User role, or with any other role that gives API…
- CVE-2024-22116 — Critical (CVSS 9.9): An administrator with restricted permissions can exploit the script execution functionality within the Monitoring Hosts…
- CVE-2020-11800 — Critical (CVSS 9.8): Zabbix Server 2.2.x and 3.0.x before 3.0.31, and 3.2 allows remote attackers to execute arbitrary code.
- CVE-2013-3738 — Critical (CVSS 9.8): A File Inclusion vulnerability exists in Zabbix 2.0.6 due to inadequate sanitization of request strings in CGI scripts,…
- CVE-2013-5743 — Critical (CVSS 9.8): Multiple SQL injection vulnerabilities in Zabbix 1.8.x before 1.8.18rc1, 2.0.x before 2.0.9rc1, and 2.1.x before 2.1.7.
Other CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities
- CVE-2026-9508 — Critical (CVSS 10.0): Incorrect permission settings on a critical resource in Suprema BioStar 2 (versions 2.9.3 through 2.9.11) that allow…
- CVE-2025-14988 — Critical (CVSS 10.0): A security issue has been identified in ibaPDA that could allow unauthorized actions on the file system under certain…
- CVE-2025-69426 — Critical (CVSS 10.0): The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) contain hardcoded credentials for an operating…
- CVE-2025-12004 — Critical (CVSS 10.0): Incorrect Permission Assignment for Critical Resource vulnerability in The Wikimedia Foundation Mediawiki - Lockdown…
- CVE-2014-125121 — Critical (CVSS 10.0): Array Networks vAPV (version 8.3.2.17) and vxAG (version 9.2.0.34) appliances are affected by a privilege escalation…
- CVE-2025-46093 — Critical (CVSS 9.9): LiquidFiles before 4.1.2 supports FTP SITE CHMOD for mode 6777 (setuid and setgid), which allows FTPDrop users to…
Browse all CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities →