<?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-05T08:45:10.318548+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-325848</id>
    <title>EUVD-2026-325848</title>
    <updated>2026-10-05T08:45:10.379386+00:00</updated>
    <content>EUVD-2026-325848</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-325848"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48488</id>
    <title>fkie_cve-2026-48488</title>
    <updated>2026-10-05T08:45:10.379426+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>phpMyFAQ is an open source FAQ web application. Prior to version 4.1.4, attachment passwords are hashed using SHA-1, a cryptographically broken algorithm. SHA-1 has been vulnerable to collision attacks since 2017 (SHAttered). Version 4.1.4 fixes the issue.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-48488"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-58fg-62fg-3fcj</id>
    <title>GHSA-58fg-62fg-3fcj — phpMyFAQ has Weak Cryptography - SHA1 for Password Hashing</title>
    <updated>2026-10-05T08:45:10.379458+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: thorsten/phpmyfaq, Packagist: phpmyfaq/phpmyfaq</p>
<p>### Summary</p>
<p>Attachment passwords are hashed using SHA-1, a cryptographically broken algorithm. SHA-1 has been vulnerable to collision attacks since 2017 (SHAttered).</p>
<p>### Details</p>
<p>**Affected File** : `phpmyfaq/src/phpMyFAQ/Attachment/AbstractAttachment.php`</p>
<p>&lt;img width="810" height="427" alt="image" src="https://github.com/user-attachments/assets/6499a008-3ece-4291-8296-f1d3303ba35c" /&gt;</p>
<p>### Impact</p>
<p>- An attacker can generate SHA-1 collisions to bypass attachment protection
- Risk of password cracking if database is compromised
- Estimated cracking time: &lt; 1 minute for standard attachment</p>
<p>### Solution</p>
<p>**Use bcrypt:**</p>
<p>```
public function setPassword(string $password): void
{
    $this-&gt;passwordHash = password_hash($password, PASSWORD_BCRYPT);
}</p>
<p>public function verifyPassword(string $plainPassword): bool
{
    return password_verify($plainPassword, $this-&gt;passwordHash);
}
```</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-58fg-62fg-3fcj"/>
  </entry>
</feed>
