Avo is a framework to create admin panels for Ruby on Rails apps. Prior to 3.32.1 and 4.0.0.beta.51, Avo's association attach workflow checks attach_<association>? in the UI and GET /resources/:resource/:id/:related/new path, but the actual write endpoint, POST /resources/:resource/:id/:related, does not run the same authorization check before mutating the association through Avo::AssociationsController#create. An authenticated low-privileged Avo user can bypass hidden or disabled attach controls and directly attach related records to a parent record by sending a crafted POST request, which can lead to privilege escalation and cross-tenant data exposure where associations represent authorization-bearing relationships. This issue is fixed in versions 3.32.1 and 4.0.0.beta.51.
References
Configurations
No configuration.
History
20 Jul 2026, 16:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/avo-hq/avo/security/advisories/GHSA-8fq9-273g-6mrg - |
17 Jul 2026, 21:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-07-17 21:17
Updated : 2026-07-23 17:58
NVD link : CVE-2026-55518
Mitre link : CVE-2026-55518
CVE.ORG link : CVE-2026-55518
JSON object : View
Products Affected
No product.
