<?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>Fri, 09 Oct 2026 09:24:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-1396 — Username Enumeration in Multiple WSO2 Products with Multi-Attribute Login Enabled</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-1396</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WSO2 Identity Server, WSO2 Open Banking IAM, WSO2 Identity Server as Key Manager&lt;/p&gt;
&lt;p&gt;A username enumeration vulnerability exists in multiple WSO2 products when Multi-Attribute Login is enabled. In this configuration, the system returns a distinct &amp;#34;User does not exist&amp;#34; error message to the login form, regardless of the validate_username setting. This behavior allows malicious actors to determine which usernames exist in the system based on observable discrepancies in the application&amp;#39;s responses.&lt;/p&gt;
&lt;p&gt;Exploitation of this vulnerability could aid in brute-force attacks, targeted phishing campaigns, or other social engineering techniques by confirming the validity of user identifiers within the system.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WSO2 Identity Server, WSO2 Open Banking IAM, WSO2 Identity Server as Key Manager&lt;/p&gt;
&lt;p&gt;A username enumeration vulnerability exists in multiple WSO2 products when Multi-Attribute Login is enabled. In this configuration, the system returns a distinct &amp;#34;User does not exist&amp;#34; error message to the login form, regardless of the validate_username setting. This behavior allows malicious actors to determine which usernames exist in the system based on observable discrepancies in the application&amp;#39;s responses.&lt;/p&gt;
&lt;p&gt;Exploitation of this vulnerability could aid in brute-force attacks, targeted phishing campaigns, or other social engineering techniques by confirming the validity of user identifiers within the system.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-1396</guid>
    </item>
  </channel>
</rss>
