<?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-14T16:10:32.125941+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-278815</id>
    <title>EUVD-2026-278815</title>
    <updated>2026-10-14T16:10:32.179879+00:00</updated>
    <content>EUVD-2026-278815</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-278815"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32629</id>
    <title>fkie_cve-2026-32629</title>
    <updated>2026-10-14T16:10:32.179919+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.1, an unauthenticated attacker can submit a guest FAQ with an email address that is syntactically valid per RFC 5321 (quoted local part) yet contains raw HTML — for example "&lt;script&gt;alert(1)&lt;/script&gt;"@evil.com. PHP's FILTER_VALIDATE_EMAIL accepts this email as valid. The email is stored in the database without HTML sanitization and later rendered in the admin FAQ editor template using Twig's |raw filter, which bypasses auto-escaping entirely. This issue has been patched in version 4.1.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-32629"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-98gw-w575-h2ph</id>
    <title>GHSA-98gw-w575-h2ph — phpMyFAQ is Vulnerable to Stored XSS via Unsanitized Email Field in Admin FAQ Editor</title>
    <updated>2026-10-14T16:10:32.179991+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
An unauthenticated attacker can submit a guest FAQ with an email address that is syntactically valid per RFC 5321 (quoted local part) yet contains raw HTML — for example "&lt;script&gt;alert(1)&lt;/script&gt;"@evil.com. PHP's FILTER_VALIDATE_EMAIL accepts this email as valid. The email is stored in the database without HTML sanitization and later rendered in the admin FAQ editor template using Twig's |raw filter, which bypasses auto-escaping entirely.</p>
<p>### Details
1. PHP FILTER_VALIDATE_EMAIL accepts RFC-valid quoted local parts with dangerous characters</p>
<p>phpmyfaq/src/phpMyFAQ/Controller/Frontend/Api/FaqController.php:99
$email = trim((string) Filter::filterVar($data-&gt;email, FILTER_VALIDATE_EMAIL));
PHP accepts "&lt;script&gt;alert(1)&lt;/script&gt;"@evil.com as a valid email (RFC 5321 allows &lt;, &gt; inside quoted local parts). Confirmed:
"&lt;script&gt;alert(1)&lt;/script&gt;"@evil.com =&gt; string (valid, not false)</p>
<p>2. Email stored raw without HTML sanitization</p>
<p>phpmyfaq/src/phpMyFAQ/Faq.php — email retrieved directly as $row-&gt;email from the database.</p>
<p>3. Admin Twig template renders email with |raw</p>
<p>phpmyfaq/assets/templates/admin/content/faq.editor.twig:296
&lt;input type="email" name="email" id="email" value="{{ faqData['email'] | raw }}" class="form-control"&gt;</p>
<p>Affected version: 4.2.0-alpha, commit f0dc86c8f</p>
<p>### PoC
**The reproduction of the vulnerability was implemented with the help of AI while reviewing the source code to generate the proof-of-concept. Please kindly note this for reference. Since…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-98gw-w575-h2ph"/>
  </entry>
</feed>
