Skip to content

Vendor

ICRTouch vulnerabilities

12 published CVES affecting ICRTouch, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
12
Critical
6
High
4
Medium
1
Low
0
Unscored
1
CISA KEV
0
Atom feed of ICRTouch alerts

Products

Latest ICRTouch CVEs

Newest publication first

  1. MediumCVSS 5.4

    ICRTouch ByTable and TouchTakeaway do not consistently implement anti-CSRF protections for state-changing web requests. The affected functionality does not require a per-session CSRF token or otherwise verify that requests originated from an authorized application context. An att...

  2. CriticalCVSS 9.1

    The order-tracking functionality in ICRTouch ByTable and TouchTakeaway does not adequately verify that a requester is authorized to access the specified order. An unauthenticated remote attacker can modify an order identifier to retrieve information associated with other customer...

  3. CriticalCVSS 9.8

    ICRTouch PocketTouch version 1.700 build 2025.3726 contains a default socket password set to the literal value password. Where the default value remains unchanged and is accepted by a TouchPoint POS terminal, an attacker with network access to the terminal’s socket service may au...

  4. HighCVSS 8.1

    The wallet top-up functionality in ICRTouch ByTable and TouchTakeaway does not adequately protect state-changing requests against CSRF. An attacker-controlled website can cause an authenticated customer’s browser to submit a wallet top-up request and add an attacker-selected char...

  5. CriticalCVSS 9.8

    ICRTouch Commander administrative login interface does not adequately restrict repeated authentication attempts. The interface also returns distinguishable responses for multiple authentication states, including different behavior when a siteID value is supplied.

  6. HighCVSS 7.5

    ICRTouch Commander administrative interface performs security-sensitive operations through HTTP GET requests and includes an API key in the request query string. GET requests are commonly retained in browser history, proxy logs, server logs, analytics systems, referrer headers, a...

  7. HighCVSS 7.5

    ICRTouch PocketTouch version 1.700 build 2025.3726 transmits the POS socket password in plaintext XML over an unencrypted TCP connection. The protocol does not provide transport-layer encryption to protect credentials from interception. An attacker able to observe network traffic...

  8. CriticalCVSS 9.8

    ICRTouch PocketTouch version 1.700 build 2025.3726 defines hard-coded default values for multiple credential fields, including a socket password and configuration and shutdown passwords. An additional email-related password field is initialized without a value.

  9. CriticalCVSS 9.1

    The PocketTouch and TouchPoint POS protocol includes a SAVECONFIG command that appears capable of overwriting till configuration files remotely. An attacker with network access to the POS socket service may be able to submit a crafted SAVECONFIG command and replace or modify term...

  10. CriticalCVSS 9.1

    The PocketTouch and TouchPoint POS CHECKPAYMENT workflow accepts a caller-supplied clerk number without adequately verifying that the requesting client is authorized to act as that clerk. An attacker with access to the POS protocol may be able to specify another employee’s clerk...

  11. HighCVSS 7.5

    The TouchOffice API clerkList endpoint appears to return sensitive clerk authentication data, including clerk PINs and iButton serial numbers. If the endpoint is accessible to callers who do not require access to these values, the API exposes reusable authentication material beyo...

  12. Unknown

    The ICRTouch white-label TouchTakeaway Cordova applications do not implement certificate or public-key pinning for backend HTTPS connections. The applications therefore rely exclusively on the device’s system trust store when validating server certificates. An attacker who can ca...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.