LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35229: Reflected XSS in discovery page of Zabbix Frontend

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.

LowCVSS 3.7Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2022-35229 is a low-severity reflected XSS issue in Zabbix Frontend’s discovery page. A logged-in user could craft a malicious link for another user, but execution also requires the victim’s current CSRF token, which changes periodically and is described as difficult to predict.

Executive priority

Handle in the next planned Zabbix maintenance window unless the frontend is broadly accessible or many untrusted users have accounts. This is not supported as an emergency issue by the provided evidence.

Technical view

The issue is CWE-79 reflected XSS affecting Zabbix Frontend versions 4.0.0-4.0.42, 5.0.0-5.0.24, 6.0.0-6.0.4, and 6.2alpha1-6.2beta3. CVSS 3.1 is 3.7 with network attack vector, high complexity, low privileges, required user interaction, and low confidentiality/integrity impact.

Likely exposure

Exposure is limited to organizations running affected Zabbix Frontend versions where authenticated users can access the discovery page and target other authenticated users.

Exploitation context

The provided sources do not show active exploitation or KEV listing. Exploitation requires authentication, victim interaction, and knowledge of the victim’s CSRF token, making practical abuse harder than typical reflected XSS.

Researcher notes

Evidence is sufficient for affected product, versions, weakness class, and exploit constraints. The bundle does not provide detailed patch version mapping, proof of exploitation, or exploit telemetry; avoid assuming more than the advisory states.

Mitigation direction

  • Identify Zabbix Frontend versions in use and compare against affected ranges.
  • Check Zabbix guidance for fixed versions or official remediation advice.
  • Apply relevant Zabbix or Debian security updates from trusted package channels.
  • Limit Zabbix Frontend access to trusted administrative networks where possible.
  • Review user permissions for accounts that can access discovery functionality.

Validation and detection

  • Inventory Zabbix Frontend instances and record exact version numbers.
  • Confirm affected versions are upgraded or covered by distribution security updates.
  • Review Zabbix logs for suspicious discovery page links involving authenticated users.
  • Verify CSRF protections and token rotation remain enabled in the deployed frontend.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-35229 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.7CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N1.22.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.7Low
CVSS 3.1 vector shape for CVE-2022-35229Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ZabbixFrontend4.0.0-4.0.42, 5.0.0-5.0.24, 6.0.0-6.0.4, 6.2alpha1-6.2beta3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.