External risk intelligence

ICRTouch Order Tracking Information Disclosure Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-122122

The vulnerability exists in web-based order-tracking functionality for a customer-facing service. Such applications are designed to be accessed by users over the internet to check order status, making them commonly deployed as internet-facing web endpoints.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability affects order-tracking features within ICRTouch ByTable and TouchTakeaway systems, allowing unauthorized access to customer order details. The issue arises because the system does not properly confirm a user's permission before granting access to specific order information, potentially exposing sensitive customer data to unauthenticated remote attackers. The primary concern is to confirm if these specific systems are in use and if they are exposed to external access.

  • Unauthorized access to customer orders.
  • Affects internet-facing order tracking.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could exploit this vulnerability by sending specially crafted requests to the order-tracking feature. Since the system does not properly check if the requester is allowed to see a specific order, the attacker can change the order identifier in the request to view details for any customer's order. This could expose sensitive customer information.

  • No authentication is required.
  • Attacker modifies order identifier in tracking request.
  • Exposes other customers' order information.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to access sensitive order information by manipulating order identifiers. This exposure could occur through the order-tracking functionality when supported by the advisory.

  • Customer order details may be exposed.
  • An attacker could guess or modify order IDs.
  • Unauthorized access to customer order history.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership

This vulnerability in ICRTouch order-tracking software requires immediate attention from teams managing customer-facing applications and the underlying infrastructure. The first practical move is to identify all instances of the affected technology, confirm their exposure and criticality to business operations, and then assign ownership for remediation. Planning should prioritize addressing the most exposed or business-critical systems first, potentially involving vendor coordination to understand available fixes or workarounds.

  • Identify system owners for all instances.
  • Verify external reachability and business criticality.
  • Plan remediation with vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is ICRTouch ByTable and TouchTakeaway?

These are software solutions designed for the hospitality industry to manage food ordering and payments. ByTable enables digital ordering for guests, while TouchTakeaway facilitates remote order processing. They function as web-based interfaces where customers interact with order-tracking features to view the status of their purchases.

What does CVE-2026-122122 mean for data security?

This vulnerability is an instance of Improper Authorization (CWE-639). It means the software fails to verify that the person requesting order information has the right to see it. Because the system lacks this check, an unauthorized user can view sensitive order details belonging to other customers.

How does an attacker trigger this vulnerability?

An attacker exploits this by interacting directly with the order-tracking web interface without needing an account or login. By simply changing or guessing an order identifier within their request, the system incorrectly serves them data associated with that ID. Simply navigating the site as a regular customer does not trigger the bug; it requires deliberate manipulation of the request parameters.

Why is this CVE considered relevant for my web services?

Halo Surface Signal notes that since this vulnerability affects web-based order-tracking tools, these systems are often intentionally deployed as internet-facing endpoints for customer convenience. If your instance is accessible over the internet to allow guests to check order statuses, it is directly exposed to this risk of unauthorized data access.

What are the first steps to address this issue?

Begin by identifying all servers running ICRTouch ByTable or TouchTakeaway in your environment. Confirm which of these are reachable from the internet and evaluate their business criticality. Once mapped, coordinate with your vendor to receive official patches or configuration guidance to secure the order-tracking functionality.

References