<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 15 Oct 2026 14:49:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-5229 — Receive Notifications After Form Submitting – Form Notify for Any Forms &lt;= 1.1.10 - Unauthenticated Authentication Bypa…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-5229</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; m615926 Receive Notifications After Form Submitting – Form Notify for Any Forms&lt;/p&gt;
&lt;p&gt;The Form Notify plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.1.10. This is due to the plugin trusting user-controlled cookie data to determine which WordPress account to authenticate after a LINE OAuth login. When LINE doesn&amp;#39;t provide an email address (which is common), the plugin falls back to reading the &amp;#39;form_notify_line_email&amp;#39; cookie value without verifying that the LINE account is associated with that email address. This makes it possible for unauthenticated attackers to gain access to any user account on the site, including administrator accounts, by completing a LINE OAuth flow with their own LINE account while injecting a malicious cookie containing the target victim&amp;#39;s email address.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; m615926 Receive Notifications After Form Submitting – Form Notify for Any Forms&lt;/p&gt;
&lt;p&gt;The Form Notify plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.1.10. This is due to the plugin trusting user-controlled cookie data to determine which WordPress account to authenticate after a LINE OAuth login. When LINE doesn&amp;#39;t provide an email address (which is common), the plugin falls back to reading the &amp;#39;form_notify_line_email&amp;#39; cookie value without verifying that the LINE account is associated with that email address. This makes it possible for unauthenticated attackers to gain access to any user account on the site, including administrator accounts, by completing a LINE OAuth flow with their own LINE account while injecting a malicious cookie containing the target victim&amp;#39;s email address.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-5229</guid>
    </item>
  </channel>
</rss>
