Quick answers
- Is CVE-2026-44306 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44306 being exploited in the wild.
- How severe is CVE-2026-44306?
- Medium severity, with a CVSS score of 5.3, published 12 May 2026.
- Which products and versions are affected?
- statamic/cms (Packagist) ECOSYSTEM:introduced=0,fixed=5.73.21; Statamic < 5.73.21, < 6.15.0, < 5.73.21, >= 6.0.0, < 6.15.0.
- Is there a fix for CVE-2026-44306?
- Yes. statamic/cms (Packagist): upgrade to 5.73.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44306 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44306?
- Check whether you run statamic/cms (Packagist) or Statamic 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
- statamic/cms (Packagist): upgrade to 5.73.21 or later
composer require statamic/cms:^5.73.21
Technical details
A CWE-204 (Observable Response Discrepancy) vulnerability exists in Statamic CMS prior to versions 5.73.21 and 6.15.0. The 'forgot password' form provided different responses depending on whether the submitted email address existed in the system. An unauthenticated, remote attacker could exploit this behavior to automate the enumeration of valid user accounts. This information disclosure facilitates subsequent credential-based attacks such as brute-forcing or targeted social engineering. The issue has been resolved by ensuring the application returns a generic, uniform response regardless of the account's existence.
Affected products
- Statamic Statamic CMS < 5.73.21, < 6.15.0
Identifiers
- CVE-2026-44306
- GHSA-m24v-f7g5-gq67
Timeline
- 2026-04-28: advisory: GitHub Security Advisory published by vendor
- 2026-05-12: disclosed: CVE published to NVD