CVE Intelligence
Skip to main content
MEDIUM

CVE-2026-22918

CVE-2026-22918 Vulnerability Analysis & Exploit Intelligence

An attacker may exploit missing protection against clickjacking by tricking users into performing unintended actions through maliciously crafted web pages, leading to the extraction of sensitive data.

Published Updated Sources: cvelistV5, SICK AG

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

sick

tdc_x401gl

CVSS base

4.3

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

Products (1)

tdc x401gl

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
4.3CVSS 3.1MEDIUMcvelistV5

Weakness & attack patterns

  • CWE-1021

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1036.004Masquerading: Masquerade Task or Service
  • T1056Input Capture
  • T1548.004Abuse Elevation Control Mechanism: Elevated Execution with Prompt

References

6 on the record

Elsewhere on this site

  • sickevery CVE for this vendor
  • CWE-1021other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.