automad/automad
Affected
- introduced
2.0.0-alpha.1, fixed2.0.0-beta.28(ecosystem)
Fixed versions
2.0.0-beta.28
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-45332
Automad has Broken Access Control: Unauthenticated exposure of administrator bcrypt password hashes and TOTP secrets via public API endpoint
Summary
A Broken Access Control vulnerability allows an unauthenticated attacker to retrieve the bcrypt password hash of every administrator account with a single POST request. The /_api/user-collection/create-first-user setup endpoint remains publicly accessible once initial configuration is complete and returns full serialized user data in the JSON response body.
Details
Affected version:
>= 2.0.0-alpha.1, <= 2.0.0-beta.272.0.0-beta.27Impact
Any Automad installation reachable over HTTP is at risk no prior account, credentials, or special network position are required to exploit this vulnerability.
Potential impacts include:
2.0.0-beta.27, the first release introducing TOTP-based two-factor authentication. If an attacker successfully recovers a plaintext password, two-factor authentication can be bypassed entirely. *Only version 2.0.0-beta.27 is affected by this specific issue.*Remediation
Update to version 2.0.0-beta.28 or later.
This issue was reported privately and fixed prior to public disclosure.
High Basis: The source's own band: HIGH
2.0.0-alpha.1, fixed 2.0.0-beta.28 (ecosystem)2.0.0-beta.28
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0