ICRTouch Commander administrative interface performs security-sensitive operations through HTTP GET requests and
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 17 Nov 2026, 20:05 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 |
|---|---|---|
| ICRTouchCommander | Affected
| Fixed in– |
AI-suggested
Users should avoid using HTTP GET requests for security-sensitive operations that include credentials in the URL. Instead, use HTTP POST requests or other secure methods to transmit sensitive data. Review and restrict access to logs and browser histories where such URLs might be stored. Monitor vendor advisories for any forthcoming patches or official guidance.
Description
The ICRTouch Commander administrative interface performs security-sensitive operations using HTTP GET requests that include an API key in the query string. Because GET requests are commonly logged and stored in various locations such as browser history, proxy logs, server logs, and referrer headers, this practice risks exposing sensitive credentials.