Skip to main content
Menu
CVEs

CVE

ICRTouch TouchPoint POS clerk impersonation in CHECKPAYMENT workflow

CVE-2026-122150EUVD-2026-127061GHSA-7785-XQ9G-H5V3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

9.1CriticalCISA-ADP
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
35/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

ICRTouch's PocketTouch and TouchPoint POS products have a flaw in the CHECKPAYMENT workflow, which accepts a clerk number from the caller without properly checking that the caller is allowed to act as that clerk. An attacker with access to the POS protocol may be able to use another employee's clerk identifier to submit payment-related requests under that person's identity.

Written by a model from the sources below. Verify against them.

Original description

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 identifier and submit payment-related requests under that identity.

cve.now Index

35Pcve.now Index 35 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.1, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 40 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-122150 (CVE-2026-122150), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-122150 (entry last updated 2026-11-17):
Affected:
- ICRTouch TouchPoint POS: from 1, through 2
- ICRTouch PocketTouch: version 1.700
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-122150 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-122150 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- http://icrtouch.com
- https://codevispera.com/research/vu-223386/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-122150
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-122150"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated

Affected versions

  • ICRTouch TouchPoint POS

    From 1 · through 2

  • ICRTouch PocketTouch

    From 1.700 · through 1.700

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-122150

Is CVE-2026-122150 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-122150?

TouchPoint POS: from 1 through 2. PocketTouch: from 1.700 through 1.700.Source: cve.now feed data

More CVEs