CVE-2026-122125: ICRTouch ByTable and TouchTakeaway do not consistently implement anti-CSRF protections for
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 17 Nov 2026, 20:05 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 5.4 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation 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 this is not a cloud service, remediation depends on vendor updates. Users should monitor vendor advisories for patches addressing CSRF protections. Until a fix is available, consider implementing compensating controls such as web application firewalls with CSRF detection rules or restricting browser-based access to trusted origins where feasible.
Description
ICRTouch ByTable and TouchTakeaway have inconsistent implementation of anti-CSRF protections for state-changing web requests. The affected functionality lacks per-session CSRF tokens or equivalent verification to confirm requests originate from authorized application contexts. This flaw allows an attacker to trick an authenticated user into submitting unauthorized requests via their active session by visiting a malicious website.