Skip to main content
Vulnerability Database/CVE-2026-110911

CVE-2026-110911: Wheels Framework SQL Injection Vulnerability

CVE-2026-110911 is a SQL injection flaw in Wheels Framework versions 1.1.8 through 4.1.1 affecting dynamic finders and query builders. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-110911 Overview

CVE-2026-110911 is a SQL injection vulnerability [CWE-89] in the Wheels CFML framework, affecting versions 1.1.8 through 4.1.1. The flaw resides in the SQL literal parser, which incorrectly treats a doubled single quote as the end of a string literal. Attackers can inject SQL through dynamic finders, query builder methods, key-based lookups, and uniqueness validators when applications pass request data directly to these APIs. Authentication flows, password-reset handlers, and token lookups are primary targets. The vendor fixed the issue in version 4.1.2.

Critical Impact

Unauthenticated attackers can manipulate SQL queries over the network to bypass authentication, extract sensitive data, or compromise database integrity in applications built on vulnerable Wheels versions.

Affected Products

  • Wheels 1.1.8 through 4.1.1 (dynamic finders, query builder where(), key-based lookups, validatesUniquenessOf)
  • Wheels 4.0.0 through 4.1.1 (query builder whereBetween() on MySQL/MariaDB with backslash escaping)
  • Fixed in Wheels 4.1.2

Discovery Timeline

  • 2026-10-15 - CVE-2026-110911 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-110911

Vulnerability Analysis

The vulnerability stems from the Wheels SQL literal parser mishandling escaped quotes. When the parser encounters a doubled single quote (''), it incorrectly interprets the sequence as the termination of a string literal rather than an escaped quote within one. Attacker-supplied values containing crafted quote sequences are re-parsed as SQL rather than treated as data.

The flaw manifests across multiple APIs that accept untrusted input. Dynamic finders such as findOneByEmail, query builder expressions where(property, value) and where(property, operator, value), string and UUID key lookups findByKey, updateByKey, deleteByKey, findOrCreateBy..., and the validatesUniquenessOf validator all route caller-supplied strings through the vulnerable parser. Numeric column values are not affected because they bypass the string-literal code path.

A secondary issue affects whereBetween() in versions 4.0.0 through 4.1.1. On MySQL and MariaDB instances configured with backslash escaping, crafted string or date bounds can alter the resulting SQL statement.

Root Cause

The parser logic does not correctly implement standard SQL quote-escaping semantics. In SQL, two consecutive single quotes inside a quoted literal represent an escaped single quote. The Wheels parser treats the second quote as the literal terminator, allowing attacker-controlled text after the sequence to be interpreted as additional SQL syntax.

Attack Vector

An unauthenticated remote attacker submits a crafted string value, such as a login email or lookup key, to a web endpoint that passes the value into an affected Wheels API. The parser prematurely terminates the literal and treats appended characters as SQL. The attacker can then alter WHERE clauses to return arbitrary rows, bypass authentication checks, exfiltrate password hashes or reset tokens, or escalate access through subsequent queries.

No authentication, user interaction, or special privileges are required. The affected methods are commonly placed in login, password-reset, and record-lookup handlers, which makes the attack surface broad in typical Wheels applications. See the GitHub Security Advisory GHSA-96rm-h22v-925x for additional technical context.

Detection Methods for CVE-2026-110911

Indicators of Compromise

  • Web server access logs containing request parameters with doubled single quotes ('') followed by SQL keywords such as OR, UNION, SELECT, or comment sequences (--, /*).
  • Database query logs showing malformed WHERE clauses, unexpected UNION operators, or boolean tautologies originating from application endpoints that use dynamic finders.
  • Spikes in authentication, password-reset, or token-lookup failures correlated with unusual input patterns.

Detection Strategies

  • Enable database query logging and alert on queries whose structure deviates from the application's known query templates.
  • Deploy a web application firewall rule set that flags doubled quote sequences in parameters bound to login, lookup, or validation endpoints.
  • Perform code review or static analysis to enumerate call sites of findOneBy*, findByKey, updateByKey, deleteByKey, findOrCreateBy*, where(), whereBetween(), and validatesUniquenessOf that receive request-scope data.

Monitoring Recommendations

  • Forward web server, application, and database audit logs to a centralized analytics platform and correlate parameter payloads with resulting SQL statements.
  • Monitor for anomalous row counts returned from authentication queries, which often indicate successful injection against login flows.
  • Track outbound data volumes from database servers to identify bulk extraction attempts following injection.

How to Mitigate CVE-2026-110911

Immediate Actions Required

  • Upgrade all Wheels deployments to version 4.1.2 or later without delay.
  • Audit application code for every call to the affected APIs and confirm that no request data reaches these methods without being passed as a parameterized value through fixed code paths.
  • Rotate any secrets, session tokens, and password-reset tokens that could have been exposed through authentication or lookup endpoints prior to patching.

Patch Information

The maintainers released Wheels 4.1.2, which corrects the SQL literal parser so that doubled single quotes are handled as escaped quotes rather than literal terminators. The fix also addresses the whereBetween() issue on MySQL and MariaDB. Review the GitHub Security Advisory GHSA-96rm-h22v-925x for upgrade instructions.

Workarounds

  • If immediate upgrade is not possible, apply strict input validation that rejects single quotes in fields passed to dynamic finders, key lookups, and uniqueness validators.
  • For MySQL and MariaDB, disable backslash escaping (NO_BACKSLASH_ESCAPES SQL mode) to reduce the whereBetween() attack surface, after testing for application compatibility.
  • Restrict database user privileges so the application account cannot read tables outside its functional scope, limiting the blast radius of successful injection.
bash
# Verify installed Wheels version and upgrade
box show wheels
box update wheels@4.1.2

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.