PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-64665 statamic CVE debrief

CVE-2026-64665 debrief: Statamic CMS OAuth login vulnerability allows unauthenticated attackers to sign in as existing users, including super admins, without passwords when using providers without verified email guarantees. This issue arises in Statamic CMS versions before 5.74.1 and 6.24.0, where OAuth login is enabled with a provider that does not guarantee verified email addresses. Exploitation requires OAuth to be explicitly enabled with such a provider, potentially leading to unauthorized access.

Vendor
statamic
Product
cms
CVSS
HIGH 8.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-06
Original CVE updated
2026-09-08
Advisory published
2026-08-06
Advisory updated
2026-09-08

Who should care

Defenders managing Statamic CMS installations, especially those using OAuth login with providers that do not enforce email verification, should assess exposure and prioritize remediation.

Why it matters

CVE-2026-64665 allows unauthenticated attackers to sign in as existing Statamic CMS users, including super admins, via OAuth providers without email verification. Defenders should verify OAuth configurations, upgrade to fixed versions, and monitor for suspicious activity.

  • Potential unauthorized access to sensitive content and administrative interfaces.
  • Risk of lateral movement within the CMS and connected systems.
  • Need for verification of OAuth provider configurations and user account integrity.
  • Priority for upgrading to fixed versions to prevent exploitation.

Technical summary

CVE-2026-64665 is a vulnerability in Statamic CMS that allows unauthenticated attackers to sign in as existing users, including super admins, via OAuth providers that do not guarantee verified email addresses. This issue is fixed in versions 5.74.1 and 6.24.0. The vulnerability arises from the application's matching of OAuth identities to accounts by email address alone, without verifying the email address through the OAuth provider. Defenders should verify OAuth configurations, upgrade to fixed versions, and monitor for suspicious activity.

Defensive priority

Defenders should prioritize verifying OAuth provider configurations, ensuring email verification, and upgrading to fixed versions 5.74.1 or 6.24.0.

Recommended defensive actions

  • Verify OAuth provider configurations to ensure email verification is enforced.
  • Upgrade Statamic CMS to version 5.74.1 or 6.24.0.
  • Review user accounts and OAuth connections for potential unauthorized access.
  • Implement additional monitoring for suspicious login activity.
  • Conduct a thorough review of existing OAuth connections and user accounts.
  • Ensure that all OAuth providers used with Statamic CMS enforce email verification.
  • Schedule regular security audits to detect and respond to potential vulnerabilities.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, which is related to OAuth login in Statamic CMS versions before 5.74.1 and 6.24.0. The vulnerability allows unauthenticated attackers to sign in as existing users, including super admins, via OAuth providers that do not guarantee verified email addresses. Evidence is based on the CVE description and NVD assessment, with limitations on source-provided information.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-64665 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-64665

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-64665 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64665

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.