Approved changes feed: RSS · Atom
cpe:2.3:a:wheels:wheels:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Wheels (6d3e4daf-c966-52d7-9e5e-0e6c67e8d220) |
|---|---|
| Product | Wheels (b38b6ec8-2239-5728-8e51-95d4127fcd23) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-111449 |
vulnerable | 2026-11-03 10:16:11.450685 |
Details available
MEDIUM (5.9)
Wheels 3.0.0 through 4.1.1 can disclose detailed exceptions when allowIPBasedDebugAccess=true (disabled by default). An allowed administrator request changes error/debug-display settings in shared application scope. If it overlaps with an unauthorized client's request that raises an error, that client can receive full exception details, including tag context or a serialized exception, and any sensitive data they contain. This race does not bypass the production gate protecting developer tools. This is fixed in 4.1.2.
Published: 2026-10-16T03:44:11.707Z
Updated: 2026-10-16T12:31:28.907Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-111445 |
vulnerable | 2026-11-03 10:16:11.389348 |
Details available
HIGH (8.1)
Wheels 4.0.0 through 4.1.2 before 4.2.0 replaces incoming scope conditions with a primary-key condition in findByKey() and exists(key=). For exists(key=), production with error information disabled returns true for an out-of-scope key instead of throwing. Applications relying on scopes for ownership or tenant authorization can therefore load and subsequently modify or delete another user's or tenant's record when the key comes from a request. The 4.2.0 fix combines key conditions with incoming scope, query-builder or where conditions in findByKey(), exists(key=), updateByKey() and deleteByKey(). Other scope-aware finders, aggregates, updateAll() and deleteAll() are not affected.
Published: 2026-10-16T03:35:00.952Z
Updated: 2026-10-19T18:42:15.796Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-111444 |
vulnerable | 2026-11-03 10:16:11.225482 |
Details available
CRITICAL (9.8)
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: 2026-10-16T03:31:30.485Z
Updated: 2026-10-16T12:32:27.499Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-111450 |
vulnerable | 2026-11-03 10:16:11.064979 |
Details available
MEDIUM (5.9)
Wheels through 4.1.1 derives its default production error-email address from the Host header of the request that starts the application. If no explicit error-email recipient is configured, a mail server is configured, and the server accepts an attacker-chosen Host, an attacker whose request triggers a cold start can direct later error emails to an address under their control for that application's lifetime. Emails disclose error and request metadata; on engines/versions where scope dumps render, they may also disclose configuration secrets and other users' session/cookie data. On the Lucee 7 engine, scope dumps fail to render, limiting disclosure to header fields. This is fixed in 4.1.2.
Published: 2026-10-16T03:49:20.178Z
Updated: 2026-10-19T18:42:08.011Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-111448 |
vulnerable | 2026-11-03 10:16:11.028400 |
Details available
LOW (3.7)
Wheels 4.0.0 through 4.1.2 uses case-insensitive comparisons in path-containment checks on case-sensitive filesystems. Canonical-path checks for zip entries, package mappings, development assets/docs, guide images and image tags can accept paths through an existing symlink to a case-distinct sibling directory, allowing access outside the intended root, including limited file disclosure. Separately, the CLI database-dump output check can write outside the application root to an existing writable case-distinct sibling directory; that action requires the CLI POST, loopback and password gate. This is fixed in 4.2.0.
Published: 2026-10-16T03:41:58.401Z
Updated: 2026-10-16T15:00:16.100Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-111446 |
vulnerable | 2026-11-03 10:16:11.001006 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-111447 |
vulnerable | 2026-11-03 10:16:10.592635 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-111443 |
vulnerable | 2026-11-03 10:16:10.536106 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-110911 |
vulnerable | 2026-11-03 10:16:01.606575 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.