Auth bypass in Diboot Diboot-Core
CVE-2026-70557
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.
Vulnerability class: IDOR (Insecure Direct Object Reference)
EPSS: 0.003 (27.3th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
Affected products
- Diboot Diboot-core — versions 0
Weakness classification (CWE)
References
- disclosure@vulncheck.com (product)
- disclosure@vulncheck.com (technical-description)
Frequently asked questions
- What is CVE-2026-70557?
- CVE-2026-70557 is a medium-severity vulnerability in Diboot Diboot-Core, classified under Authorization Bypass Through User-Controlled Key. CVSS score: 6.5/10. Published 2026-08-06.
- How severe is CVE-2026-70557?
- Medium severity. CVSS v3 base score is 6.5 out of 10.