Skip to content
Fencer Intel
low 3.7

CVE-2022-35229 json

Reflected XSS in discovery page of Zabbix Frontend

published 4y ago modified 4mo ago also EUVD-2022-38121

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

An authenticated user can create a link with reflected Javascript code inside it for the discovery page and send it to other users. The payload can be executed only with a known CSRF token value of the victim, which is changed periodically and is difficult to predict.

Patch / fix

  • zabbix zabbix 4.0.0, 5.0.25
  • zabbix Debian 14, Debian 13, Debian 12 1:6.0.7+dfsg-2

debian advisories DEBIAN-CVE-2022-35229

  • zabbix Ubuntu Pro 14.04 LTS 1:2.2.2+dfsg-1ubuntu1+esm5
  • zabbix Ubuntu Pro 16.04 LTS 1:2.4.7+dfsg-2ubuntu2.1+esm4
  • zabbix Ubuntu Pro 18.04 LTS 1:3.0.12+dfsg-1ubuntu0.1~esm4
  • zabbix Ubuntu Pro 20.04 LTS 1:4.0.17+dfsg-1ubuntu0.1~esm2
  • zabbix Ubuntu Pro 22.04 LTS 1:5.0.17+dfsg-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2022-35229

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-35229 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.22% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N

Affected products

  • Zabbix Frontend

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.