<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T03:29:51.024546+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-5946</id>
    <title>EUVD-2026-5946</title>
    <updated>2026-10-08T03:29:51.026609+00:00</updated>
    <content>EUVD-2026-5946</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-5946"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-37893</id>
    <title>fkie_cve-2024-37893</title>
    <updated>2026-10-08T03:29:51.026641+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Firefly III is a free and open source personal finance manager. In affected versions an MFA bypass in the Firefly III OAuth flow may allow malicious users to bypass the MFA-check. This allows malicious users to use password spraying to gain access to Firefly III data using passwords stolen from other sources. As OAuth applications are easily enumerable using an incrementing id, an attacker could try sign an OAuth application up to a users profile quite easily if they have created one. The attacker would also need to know the victims username and password. This problem has been patched in Firefly III v6.1.17 and up. Users are advised to upgrade. Users unable to upgrade should Use a unique password for their Firefly III instance and store their password securely, i.e. in a password manager.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-37893"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4gm4-c4mh-4p7w</id>
    <title>GHSA-4gm4-c4mh-4p7w — Firefly III has a MFA bypass in oauth flow</title>
    <updated>2026-10-08T03:29:51.026675+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: grumpydictator/firefly-iii</p>
<p>### Impact</p>
<p>A MFA bypass in the Firefly III OAuth flow may allow malicious users to bypass the MFA-check. This allows malicious users to use password spraying to gain access to your Firefly III data using passwords stolen from other sources. As OAuth applications are easily enumerable using an incrementing id, an attacker could try sign an OAuth application up to a users profile quite easily if they have created one. The attacker would also need to know the victims username and password.</p>
<p>### Patches</p>
<p>Problem has been patched in Firefly III v6.1.17 and up.</p>
<p>### Workarounds</p>
<p>- Use a unique password for your Firefly III instance,
- Store your password securely, i.e. in a password manager or in your head.</p>
<p>### References</p>
<p>- https://owasp.org/www-community/attacks/Password_Spraying_Attack
- https://www.menlosecurity.com/what-is/highly-evasive-adaptive-threats-heat/mfa-bypass</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4gm4-c4mh-4p7w"/>
  </entry>
</feed>
