Critical Injection

CVE-2026-111444 — SQL Injection in Wheels

Wheels through 4.1.2 allows SQL injection on MySQL/MariaDB with backslash escaping enabled (NO_BACKSLASH_ESCAPES absent) when an application supplies request data to inline-literal paths. These include opt-in parameterize=false queries and IN lists, and positions in developer-written where strings that the parser does not bind, such as BETWEEN bounds, function arguments and LIKE ESCAPE literals. Doubling single quotes without accounting for backslash escapes allows a value to alter the query. Bound paths are not affected; whereBetween() is bound from 4.1.2. This is fixed in 4.2.0.

Published Oct 16, 2026 · Updated Oct 16, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: mitre

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Wheels

CVSS base

9.8

Critical · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Wheels Wheels).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Wheels	Wheels	< 4.2.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
9.8	CVSS 3.1	Critical	3.9	5.9	cve@mitre.org via NIST National Vulnerability Database
9.8	CVSS 3.1	Critical	—	—	mitre via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: cve@mitre.org)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-89 · SQL Injection

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · wheels/wheels
Oct 16, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 16, 2026
CVSS changed · 9.8
Oct 16, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 16, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 16, 2026 · Alertas do Telegram
CVE published
Oct 16, 2026 · mitre

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 16, 2026 – Oct 16, 2026
1× Official description updated · Oct 16, 2026 – Oct 16, 2026

References

1 on the record

github.com/wheels-dev/wheels/security/advisories/GHSA-mvr9-2h5x-w6cq
vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

Wheels
every CVE for this vendor

Injection
same class

CWE-89
other pages naming this weakness

Related CVEs (same products)

Low CVE-2026-111448 Wheels 4.0.0 through 4.1.2 uses case-insensitive comparisons in path-containment checks… 8h
Medium CVE-2026-111449 Race Condition in Wheels 8h
Medium CVE-2026-111450 Wheels through 4.1.1 derives its default production error-email address from the Host… 8h
Medium CVE-2026-111443 Wheels 4.0.6 through 4.1.2 lets an unauthenticated client switch a request into a… 8h
High CVE-2026-111446 Incorrect Authorization in Wheels 8h
High CVE-2026-111447 Wheels 1.1 through 4.1.2 resolves nestedProperties() records by posted primary key… 8h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-111444 is "SQL Injection in Wheels", rated Critical. It affects Wheels (Wheels); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.