<?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>Form Notify &lt;= 1.1.10 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/form-notify--1.1.10/</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>Fri, 15 May 2026 09:18:37 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/form-notify--1.1.10/feed.xml" rel="self" type="application/rss+xml"/><item><title>WordPress Form Notify Plugin Authentication Bypass Vulnerability (CVE-2026-5229)</title><link>https://feed.craftedsignal.io/briefs/2026-05-form-notify-auth-bypass/</link><pubDate>Fri, 15 May 2026 09:18:37 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-form-notify-auth-bypass/</guid><description>The Form Notify plugin for WordPress is vulnerable to CVE-2026-5229, an authentication bypass, due to trusting user-controlled cookie data after a LINE OAuth login, allowing unauthenticated attackers to gain administrative access.</description><content:encoded><![CDATA[<p>The Form Notify plugin for WordPress is vulnerable to an authentication bypass vulnerability, identified as CVE-2026-5229, in versions up to and including 1.1.10. The vulnerability stems from the plugin&rsquo;s flawed logic in handling LINE OAuth logins. Specifically, when LINE does not provide an email address for a user, the plugin relies on the &lsquo;form_notify_line_email&rsquo; cookie to determine the WordPress account to authenticate. The plugin fails to validate that the LINE account is actually associated with the email address provided in the cookie, enabling attackers to forge the cookie value. This makes it possible for an unauthenticated attacker to gain access to any user account on the WordPress site, including those with administrator privileges.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker identifies a WordPress site using a vulnerable version (&lt;= 1.1.10) of the Form Notify plugin.</li>
<li>The attacker registers a LINE OAuth account.</li>
<li>The attacker initiates a LINE OAuth login flow on the target WordPress site.</li>
<li>The LINE OAuth flow does not provide an email address (this is a common scenario).</li>
<li>Before completing the login, the attacker injects a malicious &lsquo;form_notify_line_email&rsquo; cookie into their browser session, setting the value to the email address of the target victim&rsquo;s WordPress account (e.g., the administrator&rsquo;s email).</li>
<li>The attacker completes the LINE OAuth login process on the WordPress site.</li>
<li>The Form Notify plugin reads the &lsquo;form_notify_line_email&rsquo; cookie and, without proper verification, authenticates the attacker as the victim user.</li>
<li>The attacker now has full access to the victim&rsquo;s WordPress account, potentially gaining administrative control of the entire site.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-5229 allows unauthenticated attackers to bypass authentication and gain unauthorized access to WordPress accounts, including administrator accounts. This can lead to complete compromise of the WordPress site, including data theft, defacement, malware injection, and denial of service. The severity is high due to the ease of exploitation and the potential for widespread impact, particularly on sites relying on the Form Notify plugin for critical functionality.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply available patches or upgrade Form Notify plugin to a version greater than 1.1.10 to remediate CVE-2026-5229.</li>
<li>Deploy the Sigma rule <code>Detect WordPress Form Notify Authentication Bypass via Malicious Cookie</code> to your SIEM to detect potential exploitation attempts (see below).</li>
<li>Monitor web server logs for suspicious POST requests with manipulated <code>form_notify_line_email</code> cookies.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>authentication-bypass</category><category>wordpress</category><category>plugin</category><category>CVE-2026-5229</category></item></channel></rss>