CVE-2026-45332: Automad broken access control in user-collection API

CVE-2026-45332 · Severity: high · CVSS 7.5 · Published 2026-05-28

Automad, a content management system used for building websites, contains a security flaw that allows anyone on the internet to download the encrypted passwords of all administrator accounts. By sending a single request to a setup endpoint that was mistakenly left open, an attacker can obtain password hashes and, in some versions, two-factor authentication (TOTP) secrets. This could lead to full account takeover if an attacker is able to crack the passwords or bypass security measures, potentially resulting in unauthorized website changes or data theft.

Technologies: automad/automad (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-45332 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45332 being exploited in the wild.
How severe is CVE-2026-45332?
High severity, with a CVSS score of 7.5, published 28 May 2026.
Which products and versions are affected?
Automad >= 2.0.0-alpha.1, <= 2.0.0-beta.27, 2.0.0-alpha.1 to 2.0.0-beta.27; automad/automad (Packagist) >= 2.0.0-alpha.1, <= 2.0.0-beta.27, ECOSYSTEM:introduced=2.0.0-alpha.1,fixed=2.0.0-beta.28.
Is there a fix for CVE-2026-45332?
Yes. automad/automad (Packagist): upgrade to 2.0.0-beta.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45332 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-45332?
Check whether you run Automad or automad/automad (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • automad/automad (Packagist): upgrade to 2.0.0-beta.28 or later
    composer require automad/automad:^2.0.0-beta.28

Technical details

A broken access control vulnerability exists in Automad's API due to the '/_api/user-collection/create-first-user' endpoint remaining publicly accessible after initial setup. The 'createFirstUser' method in 'UserCollectionController.php' fails to verify if a user already exists before processing requests and returning serialized user data. Because the 'User' class implements a '__serialize' method that includes 'passwordHash' and 'totpSecret' (in version 2.0.0-beta.27), an unauthenticated remote attacker can trigger a POST request to this endpoint to receive the bcrypt hashes of all administrators and their TOTP secrets. This allows for offline brute-force attacks and 2FA bypass. The issue is resolved in version 2.0.0-beta.28.

Affected products

  • Automad Automad 2.0.0-alpha.1 to 2.0.0-beta.27

Identifiers

  • CVE-2026-45332
  • GHSA-xm76-r88j-vm3g

Timeline

  • 2026-05-09: advisory: GitHub Security Advisory GHSA-xm76-r88j-vm3g published
  • 2026-05-28: disclosed: CVE-2026-45332 published to NVD
  • 2026-05-28: patched: Vulnerability fixed in version 2.0.0-beta.28

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.