CVE-2026-122125: ICRTouch TouchTakeaway · Cross-Site Request Forgery
Affects ICRTouch TouchTakeawaySource CVE Database V5
Not known to be exploited.
Data as of 17 Nov 2026, 15:21 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ICRTouchTouchTakeaway | Affected
| Fixed in– |
| ICRTouchByTable | Affected
| Fixed in– |
AI-suggested
Since the vulnerability involves missing or inconsistent anti-CSRF protections, mitigation would typically involve implementing per-session CSRF tokens or equivalent verification mechanisms to ensure requests originate from authorized contexts. Users and administrators should monitor vendor advisories for official patches or updates.
Description
ICRTouch TouchTakeaway versions 1 through 2 are affected by a Cross-Site Request Forgery (CSRF) vulnerability due to inconsistent implementation of anti-CSRF protections. This flaw allows an attacker to trick an authenticated user into submitting unauthorized state-changing requests without verifying the request's origin.