How severe is GHSA-93qh-5269-9wcf?

GHSA-93qh-5269-9wcf has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-93qh-5269-9wcf?

GHSA-93qh-5269-9wcf affects the following packages: statamic/cms (Packagist), statamic/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-93qh-5269-9wcf?

Update statamic/cms to 5.74.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-93qh-5269-9wcf is resolved across your whole dependency graph.

How do I detect GHSA-93qh-5269-9wcf in my Packagist dependencies?

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.

How do I mitigate GHSA-93qh-5269-9wcf if there is no patch (or I can't update yet)?

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.

Is GHSA-93qh-5269-9wcf actively exploited in the wild?

No public exploit code has been indexed for GHSA-93qh-5269-9wcf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-93qh-5269-9wcf?

GHSA-93qh-5269-9wcf has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-93qh-5269-9wcf?

GHSA-93qh-5269-9wcf is classified as Improper Authentication (CWE-287), CWE-290 (CWE-290). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-93qh-5269-9wcf published, and has it been updated?

GHSA-93qh-5269-9wcf was published on August 6, 2026 and was last updated on August 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

Statamic: Account takeover via OAuth email matching without email-verification checkGHSA-93qh-5269-9wcf

HIGHFix: statamic/cms#14887

GHSA-93qh-5269-9wcf is a high-severity (CVSS 8.1) Improper Authentication vulnerability in statamic/cms. A fix is available for statamic/cms — see the affected versions and patch details below.

Also known asCVE-2026-64665

Published

Aug 6, 2026

Updated

Aug 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-93qh-5269-9wcf.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-93qh-5269-9wcf by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 388,997 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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, when OAuth login was 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 knowing that user's password, because the application matched OAuth identities to accounts by email address alone. Exploitation requires OAuth to be explicitly enabled with such a provider. This issue is fixed in versions 5.74.1 and 6.24.0.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`statamic/cms`	all versions	5.74.1`composer require statamic/cms:^5.74.1`
🐘Packagist	`statamic/cms`	≥ 6.0.0&&< 6.24.0	6.24.0`composer require statamic/cms:^6.24.0`

Detection & mitigation playbook

Open-source dependency

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.
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-93qh-5269-9wcf is resolved across your whole dependency graph.
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 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.