ICRTouch vulnerabilities
Every vulnerability this feed holds for ICRTouch, merged from five public registers and ordered by what warrants attention first — exploited in the wild, then CVSS, then recency.
12 vulnerabilities tracked.
- — ICRTouch ByTable and TouchTakeaway do not consistently implement anti-CSRF protections for state-changing web requests.
- — The order-tracking functionality in ICRTouch ByTable and TouchTakeaway does not adequately verify that a requester is authorized to access…
- — ICRTouch PocketTouch version 1.700 build 2025.3726 contains a default socket password set to the literal value password.
- — The wallet top-up functionality in ICRTouch ByTable and TouchTakeaway does not adequately protect state-changing requests against CSRF.
- — ICRTouch Commander administrative login interface does not adequately restrict repeated authentication attempts.
- — ICRTouch Commander administrative interface performs security-sensitive operations through HTTP GET requests and includes an API key in the…
- — ICRTouch PocketTouch version 1.700 build 2025.3726 transmits the POS socket password in plaintext XML over an unencrypted TCP connection.
- — ICRTouch PocketTouch version 1.700 build 2025.3726 defines hard-coded default values for multiple credential fields, including a socket…
- — The PocketTouch and TouchPoint POS protocol includes a SAVECONFIG command that appears capable of overwriting till configuration files…
- — The PocketTouch and TouchPoint POS CHECKPAYMENT workflow accepts a caller-supplied clerk number without adequately verifying that the…
- — The TouchOffice API clerkList endpoint appears to return sensitive clerk authentication data, including clerk PINs and iButton serial…
- — The ICRTouch white-label TouchTakeaway Cordova applications do not implement certificate or public-key pinning for backend HTTPS…
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that ICRTouch is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other vendors tracked here
Microsoft Linux Red Hat Google Apple n/a Apache Software Foundation Oracle Corporation zephyrproject Unknown Fortinet Adobe n8n-io OpenEMR Dell Drupal Cisco MONGODB erlang GitLab IBM Grafana Eclipse Foundation AMD