/

CVE-2026-55721

Severity:

CRITICAL RISK

(9.3)

SQL Injection (CWE-89) via Cookies in Storage SC

CVE-2026-55721

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Sensitive Data Exposure and Authentication Compromise

Severity:

CRITICAL RISK

(9.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Storage Concentrator (SC & SCVM) suffers from a SQL injection flaw where cookie values are directly embedded into database queries without proper sanitization.

An unauthenticated remote attacker can manipulate these cookies to exfiltrate sensitive data such as session tokens, password hashes, and stored secret keys from the backend database.

Affected context

This vulnerability affects Storage Concentrator deployments where the login.pl and debug.pl scripts consume cookie values and use them to build SQL statements.

Risk is elevated when cookies are accepted from clients without integrity protections, and when the database user that executes these queries has broad access to authentication tables or secret-storage schemas.

The issue is most pronounced in environments where input validation and query parameterization are minimal or inconsistently enforced across authentication-related endpoints.

Exploit preconditions

  • Attack surface: Public-facing web interface using login.pl and debug.pl
  • Required access: Network-level access to the HTTP service; no prior authentication needed
  • Trigger point: Submission of crafted HTTP requests with malicious cookie values
  • Why exploitation is possible: Cookie values are concatenated directly into SQL queries, bypassing input validation and parameterization, allowing the attacker to alter query logic and extract data.

Why this happens

The core issue is the construction of SQL queries by concatenating untrusted cookie data into query strings.

This aligns with CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where metacharacters such as quotes and operators from user-controlled input are interpreted by the database as part of the command.

In login.pl and debug.pl, cookies are treated as trusted state rather than external input, and the absence of prepared statements or robust escaping creates an injection channel into sensitive authentication and secrets tables.

Potential impact

  • Attackers may extract session tokens and replay them to impersonate legitimate users.
  • Attackers could obtain password hashes, enabling offline cracking and account takeover.
  • Attackers can retrieve stored secret keys, weakening encryption or signing mechanisms.
  • Attackers may enumerate or dump broader database contents, including configuration or audit data.
  • Attackers could modify authentication-related records, such as user roles or flags, leading to privilege escalation.

General mitigation guidance

Effective mitigation focuses on treating all cookie-sourced data as untrusted and eliminating dynamic query construction paths.

Recommended patterns include:

  • Using parameterized queries or stored procedures so that data cannot alter SQL control flow.
  • Applying strict validation and normalization on cookie values, limiting them to expected formats and identifiers.
  • Separating authentication and secret-storage schemas, and running queries under least-privilege database accounts with minimal read access.
  • Implementing secure session management that does not rely on opaque, unvalidated cookie data for database lookups.
  • Adopting a defense-in-depth approach with application-level access controls and monitoring around authentication tables.

How teams detect issues like this

Detection typically combines code-level and runtime approaches:

  • Static analysis rules looking for string concatenation of cookie values into SQL statements, especially in authentication-related scripts.
  • Code review checklists that flag any database operations built from request headers or cookies without parameterization.
  • Application security testing (DAST) sending tampered cookie payloads and monitoring for SQL error signatures or anomalous responses.
  • Logging and anomaly detection focused on unusual query patterns against session, credential, or secrets tables.
  • Integration of automated secure coding tools in CI pipelines to enforce policies on how queries are constructed.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-181-06.json
stonefly.comstonefly.com/contact-us/
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-181-06

Frequently asked

questions

Yes. Any remote user with network access to the affected web interface can exploit the vulnerability by sending crafted HTTP requests with malicious cookie values, even without an account.

Only basic HTTP access to the service is required; no prior authentication or local system access is needed, making this a high-risk, unauthenticated attack vector.

Replace all dynamic SQL construction involving cookie data with parameterized queries, enforce strict validation on cookie inputs, and ensure the database account used by these scripts has limited privileges to sensitive tables.

Establish secure coding standards that mandate prepared statements for all database access, treat cookies and other HTTP metadata as untrusted input, and use automated code review and testing tools to detect injection patterns early in the development lifecycle.

Find out what's already
exploitable in your codebase.