Skip to content
Noroxi
CVE-2024-22119· NVD / CVE Program· CNA Zabbix

Stored XSS in graph items select form

The cause of vulnerability is improper validation of form input field “Name” on Graph page in Items section.

MediumCVSS 5.4 · v3.1—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Feb 9, 2024
Updated
Jun 17, 2026
EPSS
0.7% · 53th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.4
CNA · Zabbix
5.5
0.1 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
zabbixzabbix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • zabbix zabbix5.0.0 and later · before 5.0.40
  • zabbix zabbix6.0.0 and later · before 6.0.24
  • zabbix zabbix6.4.0 and later · before 6.4.9
  • zabbix zabbix7.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Zabbix). Independent of NVD's CPE analysis and usually ahead of it.

  • Zabbix Zabbix

    • 5.0.0 and later · up to and including 5.0.39affected · gitfixed in 5.0.40rc1
    • 6.0.0 and later · up to and including 6.0.23affected · gitfixed in 6.0.24rc1
    • 6.4.0 and later · up to and including 6.4.8affected · gitfixed in 6.4.9rc1
    • 7.0.0alpha1 and later · up to and including 7.0.0alpha7affected · gitfixed in 7.0.0alpha8

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10zabbixbefore 1:4.0.4+dfsg-1+deb10u51:4.0.4+dfsg-1+deb10u5
Debian:12zabbixall versions—
Debian:13zabbixbefore 1:6.0.24+dfsg-11:6.0.24+dfsg-1
SUSE:Linux Enterprise Server 12 SP5zabbixbefore 4.0.12-4.27.14.0.12-4.27.1
SUSE:Package Hub 15 SP5zabbixbefore 4.0.50-bp155.3.12.14.0.50-bp155.3.12.1
SUSE:Package Hub 15 SP5zabbixbefore 4.0.50-bp155.3.12.14.0.50-bp155.3.12.1

Other highest-scoring records for the same primary product.

  • CVE-2022-23131Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAMLKEV
    98Now
  • CVE-2022-23134Possible view of the setup pages by unauthenticated users if config file already existsKEV
    80Now
  • CVE-2016-10134SQL injection vulnerability in Zabbix before 2.2.14 and 3.0 before 3.0.4 allows remote attackers to execute arbitrary SQL commands via the t
    64This week
  • CVE-2024-42327SQL injection in user.get API
    63This week
  • CVE-2013-5743Multiple 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.
    63This week
  • CVE-2024-22120Time Based SQL Injection in Zabbix Server Audit Log
    58Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Zabbix Zabbix5.0.40rc1Vendor (CNA)
Zabbix Zabbix6.0.24rc1Vendor (CNA)
Zabbix Zabbix6.4.9rc1Vendor (CNA)
Zabbix Zabbix7.0.0alpha8Vendor (CNA)
debian:zabbix1:6.0.24+dfsg-1 · Debian:13Package registry (OSV)
opensuse:zabbix4.0.50-bp155.3.12.1 · openSUSE:Leap 15.5Package registry (OSV)
suse:zabbix4.0.12-4.27.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:zabbix4.0.50-bp155.3.12.1 · SUSE:Package Hub 15 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-2212098 days apartTime Based SQL Injection in Zabbix Server Audit Log
    58Plan
  • CVE-2023-29452211 days apartRemove possibility to add html into Geomap attribution field
    40Plan
  • CVE-2023-29451211 days apartDenial of service caused by a bug in the JSON parser
    30Monitor
  • CVE-2023-32721120 days apartStored XSS in Maps element
    21Monitor
  • CVE-2024-22117291 days apartValue of sysmap_element_url can be de-synchronized causing the map element to crash when new URLs is added
    8Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

CVSS vector

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

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records