CVE-2022-24349 [Medium] | XSS in Frontend

An authenticated user can create a link with reflected XSS payload for actions’ pages, and send it to other users. Malicious code has access to all the same objects as the rest of the web page and can make arbitrary modifications to the contents of the page being displayed to a victim. This attack can be implemented with the help of social engineering and expiration of a number of factors - an attacker should have authorized access to the Zabbix Frontend and allowed network connection between a malicious server and victim’s computer, understand attacked infrastructure, be recognized by the victim as a trustee and use trusted communication channel.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-14	0.21%	0.85%	+0.64%
2	2026-03-20	0.26%	0.21%	-0.05%
3	2025-11-21	—	0.26%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-14

0.21%

0.85%

+0.64%

2026-03-20

0.26%

0.21%

-0.05%

2025-11-21

—

0.26%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.6	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.2	3.4	[email protected]
4.4	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.3	2.7	[email protected]
2.1	2.0	LOW	`AV:N/AC:H/Au:S/C:N/I:P/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:H) Exploitation requires uncommon or highly specific conditions. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	3.9	2.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.6

3.1

MEDIUM

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.2

3.4

[email protected]

4.4

3.1

MEDIUM

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.3

2.7

[email protected]

2.1

2.0

LOW

AV:N/AC:H/Au:S/C:N/I:P/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:H): Exploitation requires uncommon or highly specific conditions.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

3.9

2.9

[email protected]

OS Trackers for CVE-2022-24349

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-24349 not yet assigned priority: Debian including 1 source packages (zabbix), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-24349
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-24349/
`ubuntu`	medium	CVE-2022-24349 medium priority: Ubuntu including 1 source packages (zabbix), 14 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 7, ignored 3, needed 2, DNE 1, released 1.	https://ubuntu.com/security/CVE-2022-24349

Affected software / configurations for CVE-2022-24349

Vendor	Product	Version	Raw CPE
zabbix	frontend	>= 4.0.0, <= 4.0.38	cpe:2.3:a:zabbix:frontend::::::::
zabbix	frontend	>= 5.0.0, <= 5.0.20	cpe:2.3:a:zabbix:frontend::::::::
zabbix	frontend	>= 5.4.0, <= 5.4.10	cpe:2.3:a:zabbix:frontend::::::::
zabbix	frontend	6.0.0	cpe:2.3:a:zabbix:frontend:6.0.0:::::::*
debian	debian_linux	9.0	cpe:2.3:o:debian:debian_linux:9.0:::::::*
fedoraproject	fedora	34	cpe:2.3:o:fedoraproject:fedora:34:::::::*
fedoraproject	fedora	35	cpe:2.3:o:fedoraproject:fedora:35:::::::*

References for CVE-2022-24349

URL	Tags
https://lists.debian.org/debian-lts-announce/2022/04/msg00011.html	Third Party Advisory
https://lists.debian.org/debian-lts-announce/2023/04/msg00013.html
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2V4N22R3QVTYAJMWFK2U2O6QXAZYM35Z/
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QWP6UBFA5T6MOQPY2VDUG5YAJBFPYRFF/
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SWDZONUHDYKBXTAIAGHSYQDEGORD2QT7/
https://support.zabbix.com/browse/ZBX-20680	Issue Tracking Patch Vendor Advisory
https://lists.debian.org/debian-lts-announce/2024/10/msg00000.html

URL

CVE-2022-24349 | Reflected XSS in action configuration window of Zabbix Frontend

Exploit prediction scoring system (EPSS) score for CVE-2022-24349

Common vulnerability scoring system (CVSS) metrics for CVE-2022-24349

Weakness enumeration for CVE-2022-24349

OS Trackers for CVE-2022-24349

Affected software / configurations for CVE-2022-24349

References for CVE-2022-24349