<?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 20:16:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-9824 — User Enumeration via Response Timing</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-9824</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Mautic&lt;/p&gt;
&lt;p&gt;ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.&lt;/p&gt;
&lt;p&gt;PatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.&lt;/p&gt;
&lt;p&gt;Technical DetailsThe vulnerability was caused by different response times when:&lt;/p&gt;
&lt;p&gt;*  A valid username was provided (password hashing occurred)
  *  An invalid username was provided (no password hashing occurred)&lt;/p&gt;
&lt;p&gt;The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.&lt;/p&gt;
&lt;p&gt;WorkaroundsNo workarounds are available. Users should upgrade to the patched version.&lt;/p&gt;
&lt;p&gt;References  *   https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Mautic&lt;/p&gt;
&lt;p&gt;ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.&lt;/p&gt;
&lt;p&gt;PatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.&lt;/p&gt;
&lt;p&gt;Technical DetailsThe vulnerability was caused by different response times when:&lt;/p&gt;
&lt;p&gt;*  A valid username was provided (password hashing occurred)
  *  An invalid username was provided (no password hashing occurred)&lt;/p&gt;
&lt;p&gt;The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.&lt;/p&gt;
&lt;p&gt;WorkaroundsNo workarounds are available. Users should upgrade to the patched version.&lt;/p&gt;
&lt;p&gt;References  *   https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-9824</guid>
    </item>
  </channel>
</rss>
