LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35230: Reflected XSS in graphs page of Zabbix Frontend

An authenticated user can create a link with reflected Javascript code inside it for the graphs 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

This is a low-severity reflected cross-site scripting issue in the Zabbix Frontend graphs page. Abuse requires an authenticated user, a crafted link, victim interaction, and knowledge of the victim's CSRF token, which the source says changes periodically and is difficult to predict.

Executive priority

Handle through normal vulnerability management, not emergency response, unless affected Zabbix instances are highly exposed or used by privileged administrators.

Technical view

CVE-2022-35230 is CWE-79 reflected XSS affecting Zabbix Frontend 4.0.0-4.0.42 and 5.0.0-5.0.24. CVSS 3.1 is 3.7: network reachable, high attack complexity, low privileges required, user interaction required, and limited confidentiality and integrity impact.

Likely exposure

Exposure is limited to organizations running the listed Zabbix Frontend versions, especially where multiple authenticated users access the web interface and may receive internal links.

Exploitation context

The source bundle does not show active exploitation or KEV listing. Practical exploitation appears constrained because the attacker needs authentication, must lure a victim to open a link, and must know a current victim CSRF token.

Researcher notes

The key limiting condition is the victim CSRF token requirement. Evidence is sufficient for affected versions and impact type, but the bundle does not include proof of exploitation, detailed patch identifiers, or full vendor remediation text.

Mitigation direction

  • Upgrade Zabbix Frontend outside the affected version ranges.
  • Apply Debian LTS zabbix security updates where Debian packages are used.
  • Review Zabbix advisory ZBX-21305 for vendor remediation guidance.
  • Limit Zabbix Frontend access to trusted users and networks.
  • Warn administrators not to open unsolicited Zabbix graph links.

Validation and detection

  • Inventory deployed Zabbix Frontend versions against the affected ranges.
  • Confirm Debian systems include the referenced LTS zabbix security update.
  • Review Zabbix Frontend logs for unusual graph page links or parameters.
  • Check whether exposed instances require authentication and network restrictions.
  • Track ZBX-21305 for any vendor clarification or follow-up fixes.
Prepared
Confidence
high
Sources
5

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-35230 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
4Source 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-35230Attack 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.24Listed
Weakness

CWE details

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