CVE-2026-122125

CVE-2026-122125

Published Nov 17, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
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 attacker who convinces an authenticated user to visit a malicious website may cause the user’s browser to submit unauthorized requests to the platform using the user’s active session.

Analysis

AI-generated

Technical impact

The vulnerability stems from the lack of consistent anti‑CSRF protection on state‑changing HTTP endpoints in ICRTouch ByTable and TouchTakeaway. An attacker who lures an authenticated user to a malicious site can make the user’s browser submit arbitrary requests using the user’s active session, thereby modifying or deleting data without the user’s consent. This weakness permits the attacker to alter data, trigger undesired business actions, or otherwise abuse the authenticated context, undermining both integrity and confidentiality.

Affected Systems

Affected vendors are ICRTouch, with products ByTable and TouchTakeaway. No specific version information is disclosed; any installation of these products that lacks CSRF defense is vulnerable.

Risk and Exploitability

The EPSS score is not available and the vulnerability is not listed in CISA KEV, indicating no confirmed public exploits yet. However, CSRF is a common attack vector for web applications, and the absence of a per‑session token or origin check means that any user who visits a malicious page while authenticated can be coerced into sending unwanted requests. Because the flaw does not rely on a privileged circumstance and merely requires an online user, the risk level is moderate to high, pending a vendor patch or fixed release.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Implement a per‑session CSRF token mechanism (e.g., synchronous random token in each form and validate on the server) for all endpoints that change state.
  • Enforce strict Origin and Referer header validation on state‑changing requests to ensure they originate from trusted domains.
  • Until a patch is available, remove or restrict access to any state‑changing endpoints that lack CSRF protection, or force a manual confirmation step for sensitive actions.

Generated by OpenCVE AI on November 17, 2026 at 16:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-352
Type Values Removed Values Added
Description 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 attacker who convinces an authenticated user to visit a malicious website may cause the user’s browser to submit unauthorized requests to the platform using the user’s active session.
Title CVE-2026-122125
References

Subscriptions

No data.

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
certcc
Published
Updated
Nov 17, 2026, 3:05 PM
Reserved
Nov 4, 2026, 6:11 PM
Status
Received
Published
Nov 17, 2026, 4:17 PM
Modified
Nov 17, 2026, 4:17 PM