Statamic: Account takeover via OAuth email matching without email-verification check
Published 6 Aug 2026 · Updated 6 Aug 2026
Affected packages
- Affected
- <5.74.1
- Fixed in
- 5.74.1
composer require statamic/cms:^5.74.1- Affected
- >=6.0.0 <6.24.0
- Fixed in
- 6.24.0
composer require statamic/cms:^6.24.0Details
Impact
When OAuth login is enabled with a provider that does not guarantee verified email addresses, an unauthenticated attacker could sign in as an existing user — potentially including a super admin — without their password. Exploitation requires OAuth to be explicitly enabled with such a provider.
Patches
Fixed in 5.74.1 and 6.24.0.
Workarounds
Only enable OAuth with providers that guarantee verified email addresses, or disable OAuth login.
Is GHSA-93qh-5269-9wcf in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected statamic/cms, and gives you the command that fixes it.
References
- Linkgithub.com/statamic/cms/security/advisories/GHSA-93qh-5269-9wcf
- Linkgithub.com/statamic/cms/pull/14887
- Linkgithub.com/statamic/cms/commit/e59dd342c83bc45de26573cfb0536a0bca98255a
- Packagegithub.com/statamic/cms
- Linkgithub.com/statamic/cms/releases/tag/v5.74.1
- Linkgithub.com/statamic/cms/releases/tag/v6.24.0
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.