<?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, 08 Oct 2026 13:25:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-8457 — WooCommerce - Social Login &lt;= 2.8.7 - Unauthenticated Authentication Bypass via Forged Apple 'id_token' JWT</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-8457</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WPWeb WooCommerce - Social Login&lt;/p&gt;
&lt;p&gt;The WooCommerce - Social Login plugin for WordPress is vulnerable to Authentication Bypass in all versions up to and including 2.8.7. This is due to the plugin&amp;#39;s Apple login handler accepting the Apple id_token and decoding only its base64 payload without verifying the JWT signature against Apple&amp;#39;s public keys or validating the issuer, audience, or expiry claims, combined with the security nonce required to invoke the login flow being publicly exposed to unauthenticated users via a localized JavaScript object on the login page. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by supplying a forged id_token whose payload contains the target user&amp;#39;s email address, as that email is used without any role exclusion to resolve a WordPress account and immediately issue an authenticated session for it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WPWeb WooCommerce - Social Login&lt;/p&gt;
&lt;p&gt;The WooCommerce - Social Login plugin for WordPress is vulnerable to Authentication Bypass in all versions up to and including 2.8.7. This is due to the plugin&amp;#39;s Apple login handler accepting the Apple id_token and decoding only its base64 payload without verifying the JWT signature against Apple&amp;#39;s public keys or validating the issuer, audience, or expiry claims, combined with the security nonce required to invoke the login flow being publicly exposed to unauthenticated users via a localized JavaScript object on the login page. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by supplying a forged id_token whose payload contains the target user&amp;#39;s email address, as that email is used without any role exclusion to resolve a WordPress account and immediately issue an authenticated session for it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-8457</guid>
    </item>
  </channel>
</rss>
