NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

Statamic: Missing authorization on Control Panel endpoint allows disclosure of user existenceGHSA-225x-3jhx-wh4q

MEDIUMFix: statamic/cms#14905

GHSA-225x-3jhx-wh4q is a medium-severity (CVSS 4.3) Information Exposure vulnerability in statamic/cms. A fix is available for statamic/cms — see the affected versions and patch details below.

Also known asCVE-2026-64664
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-225x-3jhx-wh4q.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk
0.00%0.28%0.56%0.84%0.3%0.3%Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐘statamic/cms🐘statamic/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.74.1 and 6.24.0, an authenticated Control Panel user could use an endpoint intended for the user creation wizard to determine if a given email address belonged to an existing user, without having permission to view users, though the endpoint only exposed user existence and not any other user data. This issue is fixed in versions 5.74.1 and 6.24.0.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagiststatamic/cmsall versions5.74.1composer require statamic/cms:^5.74.1
🐘Packagiststatamic/cms≥ 6.0.0&&< 6.24.06.24.0composer require statamic/cms:^6.24.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for statamic/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update statamic/cms to 5.74.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-225x-3jhx-wh4q is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact An authenticated Control Panel user could use an endpoint intended for the user creation wizard to determine if a given email address belongs to an existing user, without having permission to view users. The endpoint only exposed user existence, not any of its data. ### Patches This has been fixed in 5.74.1 and 6.24.0.
O3 Security · Impact-Aware SCA

Is GHSA-225x-3jhx-wh4q in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Statamic: Missing authorization on Control Panel…