Vulnerability · Published Aug 6, 2026 · Assigned by VulnCheck
CVE-2026-70557diboot-core Authenticated Arbitrary Field Read via loadRelatedData Discloses Password Hashes and Salts
Medium 6.5
In plain English
A medium-severity authorization bypass via user-controlled key in diboot-core from diboot. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 33% of all known vulnerabilities).
Official description
diboot-core's POST /common/load-related-data endpoint resolves caller-supplied field names to any @TableField column of any entity and returns those values for all rows, with no field or entity allowlist. The only guard, relatedDataSecurityCheck(), returns true unconditionally, so any authenticated user (including a zero-role account) can read @JsonIgnore-annotated secret fields such as IamAccount.authSecret and IamAccount.secretSalt for every account, or arbitrary secret fields of any other entity. Shiro's two-iteration MD5 with an 8-character salt is trivially crackable offline, so the disclosed admin password hashes convert to full administrative takeover. The endpoint is not example code; the official diboot-admin-ui frontend requires it, so deployments following the vendor's recommended integration expose it. The mechanism was renamed relatedData* to attachMore* on the development branch, but attachMoreSecurityCheck() also returns true unconditionally.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| diboot | diboot-core | 0 – through 3.9.0 |
Weakness: CWE-639 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
References
- https://github.com/dibo-software/diboot product
- https://github.com/dibo-software/diboot/issues/104 technical-description