<?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>Tue, 27 Oct 2026 14:24:32 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-02348</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-02348</link>
      <description>bdu:2024-02348</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-02348</guid>
    </item>
    <item>
      <title>EUVD-2026-4359</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-4359</link>
      <description>EUVD-2026-4359</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-4359</guid>
    </item>
    <item>
      <title>fkie_cve-2024-27299</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-27299</link>
      <description>&lt;p&gt;phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. A SQL injection vulnerability has been discovered in the the &amp;#34;Add News&amp;#34; functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE. The vulnerable field lies in the  `authorEmail` field which uses PHP&amp;#39;s `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability. This vulnerability is fixed in 3.2.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. A SQL injection vulnerability has been discovered in the the &amp;#34;Add News&amp;#34; functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE. The vulnerable field lies in the  `authorEmail` field which uses PHP&amp;#39;s `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability. This vulnerability is fixed in 3.2.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-27299</guid>
    </item>
    <item>
      <title>GHSA-qgxx-4xv5-6hcw — phpMyFAQ SQL Injection at "Save News"</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qgxx-4xv5-6hcw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpmyfaq/phpmyfaq&lt;/p&gt;
&lt;p&gt;### Summary
A SQL injection vulnerability has been discovered in the the &amp;#34;Add News&amp;#34; functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerable field lies in the  `authorEmail` field which uses PHP&amp;#39;s `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability.&lt;/p&gt;
&lt;p&gt;### PoCs
4 PoCs are demonstrated here to illustrate the potential impacts.&lt;/p&gt;
&lt;p&gt;#### PoC 1 - Postgres Time Based SQLi
1. Login as admin or any user with the rights to view and save news.
2. Navigate to &amp;#34;../phpmyfaq/admin/?action=news&amp;#34;, click on &amp;#34;Add news&amp;#34;, fill in some data, send and intercept the request.
3. Modify the intercepted &amp;#34;/admin/?action=save-news&amp;#34; request to look like the SS below:
    3.1 - Set the &amp;#34;authorEmail&amp;#34; field in the body to &amp;#34;`test&amp;#39;/*@[email.com](http://email.com/)`&amp;#34;.
    3.2 - Set the &amp;#34;linkTitle&amp;#34; field in the body to &amp;#34;`*/,1,1,1,1,1,1,1);select+pg_sleep(5)--`&amp;#34;.
    3.3 - Set the rest of the fields as empty and send the request.
4. Notice the 5s delay in the response time, indicating that the sleep function was executed, verifying the existence of the SQ…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpmyfaq/phpmyfaq&lt;/p&gt;
&lt;p&gt;### Summary
A SQL injection vulnerability has been discovered in the the &amp;#34;Add News&amp;#34; functionality due to improper escaping of the email address. This allows any authenticated user with the rights to add/edit FAQ news to exploit this vulnerability to exfiltrate data, take over accounts and in some cases, even achieve RCE.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerable field lies in the  `authorEmail` field which uses PHP&amp;#39;s `FILTER_VALIDATE_EMAIL` filter. This filter is insufficient in protecting against SQL injection attacks and should still be properly escaped. However, in this version of phpMyFAQ (3.2.5), this field is not escaped properly can be used together with other fields to fully exploit the SQL injection vulnerability.&lt;/p&gt;
&lt;p&gt;### PoCs
4 PoCs are demonstrated here to illustrate the potential impacts.&lt;/p&gt;
&lt;p&gt;#### PoC 1 - Postgres Time Based SQLi
1. Login as admin or any user with the rights to view and save news.
2. Navigate to &amp;#34;../phpmyfaq/admin/?action=news&amp;#34;, click on &amp;#34;Add news&amp;#34;, fill in some data, send and intercept the request.
3. Modify the intercepted &amp;#34;/admin/?action=save-news&amp;#34; request to look like the SS below:
    3.1 - Set the &amp;#34;authorEmail&amp;#34; field in the body to &amp;#34;`test&amp;#39;/*@[email.com](http://email.com/)`&amp;#34;.
    3.2 - Set the &amp;#34;linkTitle&amp;#34; field in the body to &amp;#34;`*/,1,1,1,1,1,1,1);select+pg_sleep(5)--`&amp;#34;.
    3.3 - Set the rest of the fields as empty and send the request.
4. Notice the 5s delay in the response time, indicating that the sleep function was executed, verifying the existence of the SQ…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qgxx-4xv5-6hcw</guid>
    </item>
    <item>
      <title>gsd-2024-27299</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-27299</link>
      <description>gsd-2024-27299</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-27299</guid>
    </item>
  </channel>
</rss>
