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

CVE-2026-111447: Wheels Privilege Escalation Vulnerability

CVE-2026-111447 is a privilege escalation flaw in Wheels framework versions 1.1 through 4.1.2 that allows unauthorized manipulation of nested form records. 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-111447 Overview

CVE-2026-111447 is an insecure direct object reference flaw in the Wheels framework affecting versions 1.1 through 4.1.2. The nestedProperties() function resolves child records by posted primary key without verifying ownership by the parent being saved. An authenticated user submitting a nested form for their own parent record can reassign, update, or delete hasMany, hasOne, and belongsTo rows that belong to other parents. New child rows with composite primary keys unrelated to foreign keys retain attacker-posted key values, letting the request dictate record identity. The issue is tracked under [CWE-472: External Control of Assumed-Immutable Web Parameter] and resolved in Wheels 4.2.0.

Critical Impact

Authenticated users can tamper with, reassign, or delete other users' nested records by posting arbitrary primary keys through nested form submissions.

Affected Products

  • Wheels framework versions 1.1 through 4.1.2
  • Applications using nestedProperties() with hasMany, hasOne, or belongsTo associations
  • Wheels applications with allowDelete=true on nested associations

Discovery Timeline

  • 2026-10-16 - CVE-2026-111447 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-111447

Vulnerability Analysis

The Wheels Object-Relational Mapper (ORM) exposes a nestedProperties() capability that lets a parent model accept nested data for its associated child records. When processing posted form data, the framework resolves each child record by its posted primary key and binds it to the parent being saved.

The resolution step does not confirm that the retrieved child actually belongs to the parent. Any authenticated user able to submit a nested form for a record they own can supply primary keys referencing child rows that belong to unrelated parents. The framework loads those rows and applies the submitted changes.

The same weakness extends to multiple association types. hasMany and hasOne rows can be reassigned to the attacker's parent, and deleted outright when allowDelete=true is configured. belongsTo records can be edited by posting the key of an associated record owned by another user. For new child records whose composite primary keys are not derived from foreign keys, the posted key values are retained, letting the request choose the identity of newly created rows.

Root Cause

The root cause is a missing authorization check between the parent object and nested child identifiers submitted through user-controlled input. The framework treats the posted primary key as an assumed-immutable identifier and skips the parent-child ownership validation before applying updates or deletes.

Attack Vector

Exploitation requires authenticated access and the ability to submit a nested form for a record the attacker legitimately owns. The attacker modifies the hidden primary key fields in the nested payload to reference records belonging to other users. The server-side nestedProperties() handler loads those records and applies the attacker's modifications, including deletion when permitted. Refer to the GitHub Security Advisory GHSA-6979-65wv-7pxq for additional technical detail.

Detection Methods for CVE-2026-111447

Indicators of Compromise

  • Nested form submissions containing primary key values that do not correspond to the authenticated user's parent record
  • Unexpected modifications or deletions of hasMany, hasOne, or belongsTo child records without a corresponding direct action by their owner
  • Creation of new child rows with composite primary keys whose values were supplied by the client rather than derived server-side

Detection Strategies

  • Audit application logs for POST and PUT requests to controllers that invoke nestedProperties() and compare submitted child IDs against ownership metadata
  • Enable database-level audit trails on tables backing nested associations to flag updates where the acting user does not own the parent record
  • Review web server access logs for parameter tampering patterns in nested form payloads, particularly hidden id fields

Monitoring Recommendations

  • Alert on nested association updates where the modifying session's user ID does not match the owning user ID of the affected child row
  • Monitor volume anomalies in deletions on associations configured with allowDelete=true
  • Capture full request bodies for nested form endpoints during incident investigation to reconstruct exploit attempts

How to Mitigate CVE-2026-111447

Immediate Actions Required

  • Upgrade the Wheels framework to version 4.2.0 or later, which enforces parent-child ownership checks in nestedProperties()
  • Review all models that enable nestedProperties with allowDelete=true and temporarily disable deletion until the patch is applied
  • Audit recent database activity on nested association tables to identify any unauthorized modifications

Patch Information

The vulnerability is fixed in Wheels 4.2.0. The patch ensures that nested child records are resolved only when they already belong to the parent being saved, and that posted primary keys for new composite-key children are no longer honored when they are not composed of foreign keys. See the GitHub Security Advisory GHSA-6979-65wv-7pxq for the complete fix description.

Workarounds

  • Add server-side authorization checks in controllers that process nested forms to verify that each submitted child ID belongs to the current user's parent before saving
  • Strip or ignore client-supplied primary key fields in nested payloads for new child records with composite keys
  • Disable allowDelete on nested associations until the application is upgraded to 4.2.0

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.