External risk intelligence

PocketTouch and TouchPoint POS Clerk Identifier Impersonation Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-122150

The vulnerability exists within a Point of Sale (POS) protocol. While these systems operate over a network, they are typically deployed within private, segmented local area networks or secure internal environments rather than being directly exposed to the public internet. Access from the public internet would be atypical and generally restricted by internal controls or network segmentation.

Authentication Bypass

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in a Point of Sale (POS) payment workflow that could allow an attacker to impersonate another employee. This issue stems from the system accepting a clerk number without sufficient verification of authorization, potentially enabling unauthorized payment-related actions under a different identity. The main concern at this time is confirming the relevance and exposure of this vulnerability to our specific environment.

  • Unauthorized access to employee payment functions.
  • Confirms potential for unauthorized actions by attackers.
  • Assess if this POS system is in use.

Attack Path

How an attacker could exploit the issue

An attacker who can interact with the Point of Sale (POS) protocol can potentially impersonate another employee. By supplying a different clerk's identifier when submitting payment requests, the attacker could perform actions as that employee. This could lead to unauthorized access to payment information and the ability to manipulate payment processes.

  • Requires access to the POS protocol.
  • Triggers by supplying a caller-supplied clerk number.
  • Risk of unauthorized actions as another employee.

Live Threat

Current exploitation, exposure, and threat context

A vulnerability in the `CHECKPAYMENT` workflow could allow an attacker to impersonate another employee when submitting payment requests, provided they can access the POS protocol. This could affect financial transactions processed through the Point of Sale system.

  • Payment transaction data.
  • Unauthorized actions via another employee's ID.
  • Potentially misdirected or fraudulent transactions.

Operational Fix

Recommended remediation, mitigation, and detection steps

The `CHECKPAYMENT` workflow in PocketTouch and TouchPoint POS systems is vulnerable to unauthorized actions, potentially allowing attackers to impersonate other employees. This issue is likely the responsibility of the Point of Sale (POS) application owner, working closely with the infrastructure or platform team managing the POS environment and potentially the network/security team if exposure is broader than anticipated. The first practical step is to identify all instances of PocketTouch and TouchPoint, confirm their network accessibility and business criticality, and then engage with the identified owner to prioritize and plan remediation, which may involve vendor coordination.

  • Identify POS system owners and scope.
  • Verify network reachability and business impact.
  • Plan remediation with vendor support.

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 PocketTouch and TouchPoint POS?

These are Point of Sale (POS) software solutions used in retail and hospitality environments to manage financial transactions. They function as the digital interface where staff process payments and manage sales workflows. The affected `CHECKPAYMENT` component is a specific part of these systems designed to handle the messaging and logic required to finalize customer payments during a transaction.

What does CWE-287 mean for CVE-2026-122150?

CWE-287 refers to Improper Authentication. In the context of this CVE, it means the software fails to confirm that a user is truly who they claim to be when submitting a payment request. Instead of validating the identity of the person making the request, the system blindly trusts the clerk number provided in the data, allowing the software to process commands as if they originated from the impersonated user.

How can an attacker trigger this vulnerability?

An attacker must have network access to communicate directly with the POS protocol. By crafting a request that includes a different employee's clerk identifier in the `CHECKPAYMENT` workflow, they can deceive the system. It is important to note that simply being on the same local network is not a trigger; the attacker must be capable of sending formatted commands specifically understood by the POS service to impersonate an authorized staff member.

Do I need to worry if my POS is internal?

Halo Surface Signal indicates this vulnerability is unlikely to be reachable from the public internet, as these POS systems are typically isolated within private, segmented local networks. If your system is correctly firewalled and not bridged to external traffic, the risk of remote exploitation is significantly lower compared to a system directly exposed to the web.

How should I respond to this threat?

Start by auditing your environment to locate all active instances of PocketTouch and TouchPoint software. Once mapped, confirm their network placement to see if they are isolated as intended. Coordinate with your POS system administrators to discuss vendor-provided updates or configuration changes, and ensure that access to the POS protocol is restricted to only the necessary internal devices.

References