<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Statamic CMS - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/statamic-cms/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 06 Aug 2026 21:29:58 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/statamic-cms/feed.xml" rel="self" type="application/rss+xml"/><item><title>Statamic CMS Account Takeover via Unverified OAuth Email Matching</title><link>https://feed.craftedsignal.io/briefs/2026-08-statamic-oauth-takeover/</link><pubDate>Thu, 06 Aug 2026 21:29:58 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-statamic-oauth-takeover/</guid><description>An unauthenticated attacker can achieve account takeover by leveraging unverified OAuth email matching in Statamic CMS, allowing unauthorized authentication as existing users including administrators.</description><content:encoded><![CDATA[<p>Statamic CMS versions prior to 5.74.1 and versions in the 6.0.0 through 6.23.x series are vulnerable to an account takeover flaw, tracked as CVE-2026-64665. The vulnerability resides in the OAuth authentication flow, where the application improperly associates incoming OAuth responses with local user accounts based solely on email addresses, without verifying that the email address is marked as verified by the identity provider.</p>
<p>If an administrator has enabled an OAuth provider that does not mandate email verification, an attacker can register an account at the identity provider using an email address belonging to an existing Statamic user. Upon successful OAuth authentication, the Statamic application incorrectly maps the attacker's session to the existing target account, granting the attacker full access to that user's privileges, including super-administrator rights. This bypasses standard password-based authentication and two-factor authentication, significantly increasing the risk of full site compromise.</p>
<h2 id="impact">Impact</h2>
<p>The vulnerability allows unauthenticated attackers to hijack accounts, including highly privileged administrator accounts. Successful exploitation leads to full site administration, potentially enabling data exfiltration, backdooring the application, or modifying site content. The scope affects all Statamic deployments where OAuth is enabled with non-strictly configured third-party providers.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Statamic CMS to version 5.74.1 or 6.24.0 immediately to apply the fix for CVE-2026-64665.</li>
<li>Review OAuth provider configurations in the Statamic control panel and ensure that only identity providers providing verified email attributes are in use.</li>
<li>If current identity providers do not guarantee email verification, disable OAuth authentication until providers with secure configurations can be implemented.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>oauth</category><category>account-takeover</category><category>cms</category><category>authentication-bypass</category></item></channel></rss>