Skip to main content
VulnerabilityPublished Updated

CVE-2026-45332: marcantondahmen automad · Information Exposure

Affects marcantondahmen automadSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High : upgrade to 2.0.0-beta.28 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.0-beta.28
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

  2. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade marcantondahmen automad to 2.0.0-beta.28.

Affected software

ProductAffectedFixed in
marcantondahmenautomadAffected
  • >=2.0.0-alpha.1 <2.0.0-beta.28
Fixed in
  • 2.0.0-beta.28

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Automad to version 2.0.0-beta.28 or later, where this vulnerability is fixed. Since this is a self-hosted product, users must apply the update themselves. Patch status is not explicitly stated in the vendor advisory but the description confirms the fix in 2.0.0-beta.28. Until patched, restrict access to the /_api/user-collection/create-first-user endpoint if possible.

Description

Automad is a flat-file content management system and template engine. From 2.0.0-alpha.1 to 2.0.0-beta.27, 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. This vulnerability is fixed in 2.0.0-beta.28.

References

Community reviews

Loading reviews…