PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-110911 – SQL Injection – Wheels 1.1.8 through 4.1.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-110911 is a critical SQL injection vulnerability (CWE-89) in the Wheels framework, affecting versions 1.1.8 through 4.1.1. Applications that pass request-supplied data to certain Wheels data-access APIs can be manipulated by unauthenticated remote attackers. The CVSS v3.1 base score is 9.8 (Critical).

Technical details

  • Root cause: The framework quotes caller-supplied values and passes them through its WHERE parser. The parser incorrectly treats a doubled single quote ('') as the end of a string literal instead of an escaped quote, so an attacker can break out of the literal and inject SQL.
  • Affected components: dynamic finders (e.g. findOneByEmail(), findAllByUsername()), query builder where() methods, key-based lookups (findByKey, updateByKey, deleteByKey), and uniqueness validation checks. In versions 4.0.0–4.1.1, whereBetween() on string/date columns is also affected, including on MySQL/MariaDB with backslash escaping enabled.
  • Trigger conditions: The application passes request-supplied values to these APIs. The advisory gives the example nomatch' OR email<>', which changes the query logic. Numeric columns are protected by validation.
  • Attack vector: Network, with no authentication or user interaction required.
  • Impact: Authentication and password-reset bypass, row enumeration and data exfiltration, and manipulation of query logic through injected SQL.

Affected software

  • Wheels 1.1.8 through 4.1.1 (inclusive)
  • whereBetween() issue: Wheels 4.0.0 through 4.1.1

Severity

  • CVSS v3.1 base score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to Wheels 4.1.2. This version binds values as query parameters instead of quoting them into SQL strings.
  • If you cannot patch yet: The vendor suggests the following workarounds:
    • Validate and whitelist request values before passing them to these APIs.
    • Use numeric primary key lookups where feasible.
    • Use explicit parameter binding with where clauses.
  • Review application code paths where request data reaches dynamic finders, where(), key-based lookups, and uniqueness validations.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge