<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 19:36:15 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-82842</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-82842</link>
      <description>&lt;p&gt;The SAML Single Sign On  WordPress plugin before 6.0.0 does not honour the configured criterion for linking an incoming single sign-on identity to a WordPress account, always resolving the identity by login name whatever the site has chosen, which allows an attacker who can have the site&amp;#39;s identity provider assert a login name of their choosing to authenticate as any account, including an administrator, without proving ownership of that account.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The SAML Single Sign On  WordPress plugin before 6.0.0 does not honour the configured criterion for linking an incoming single sign-on identity to a WordPress account, always resolving the identity by login name whatever the site has chosen, which allows an attacker who can have the site&amp;#39;s identity provider assert a login name of their choosing to authenticate as any account, including an administrator, without proving ownership of that account.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-82842</guid>
    </item>
    <item>
      <title>GHSA-c354-pg28-5955</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-c354-pg28-5955</link>
      <description>&lt;p&gt;The SAML Single Sign On  WordPress plugin before 6.0.0 does not honour the configured criterion for linking an incoming single sign-on identity to a WordPress account, always resolving the identity by login name whatever the site has chosen, which allows an attacker who can have the site&amp;#39;s identity provider assert a login name of their choosing to authenticate as any account, including an administrator, without proving ownership of that account.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The SAML Single Sign On  WordPress plugin before 6.0.0 does not honour the configured criterion for linking an incoming single sign-on identity to a WordPress account, always resolving the identity by login name whatever the site has chosen, which allows an attacker who can have the site&amp;#39;s identity provider assert a login name of their choosing to authenticate as any account, including an administrator, without proving ownership of that account.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-c354-pg28-5955</guid>
    </item>
  </channel>
</rss>
