<?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, 22 Oct 2026 19:00:35 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-261006</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-261006</link>
      <description>EUVD-2026-261006</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-261006</guid>
    </item>
    <item>
      <title>fkie_cve-2025-62519</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-62519</link>
      <description>&lt;p&gt;phpMyFAQ is an open source FAQ web application. Prior to version 4.0.14, an authenticated SQL injection vulnerability in the main configuration update functionality of phpMyFAQ allows a privileged user with &amp;#39;Configuration Edit&amp;#39; permissions to execute arbitrary SQL commands. Successful exploitation can lead to a full compromise of the database, including reading, modifying, or deleting all data, as well as potential remote code execution depending on the database configuration. This issue has been patched in version 4.0.14.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;phpMyFAQ is an open source FAQ web application. Prior to version 4.0.14, an authenticated SQL injection vulnerability in the main configuration update functionality of phpMyFAQ allows a privileged user with &amp;#39;Configuration Edit&amp;#39; permissions to execute arbitrary SQL commands. Successful exploitation can lead to a full compromise of the database, including reading, modifying, or deleting all data, as well as potential remote code execution depending on the database configuration. This issue has been patched in version 4.0.14.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-62519</guid>
    </item>
    <item>
      <title>GHSA-fxm2-cmwj-qvx4 — phpMyFAQ has Authenticated SQL Injection in Configuration Update Functionality</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fxm2-cmwj-qvx4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: thorsten/phpmyfaq, Packagist: phpmyfaq/phpmyfaq&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An authenticated SQL injection vulnerability in the main configuration update functionality of phpMyFAQ (v4.0.13 and prior) allows a privileged user with &amp;#39;Configuration Edit&amp;#39; permissions to execute arbitrary SQL commands. Successful exploitation can lead to a full compromise of the database, including reading, modifying, or deleting all data, as well as potential remote code execution depending on the database configuration.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability exists in the `save` method within the `src/phpMyFAQ/Controller/Administration/ConfigurationTabController.php` controller. This method handles the saving of application-wide configuration settings. It retrieves all submitted form data as an associative array via `$request-&amp;gt;get(&amp;#39;edit&amp;#39;)`.&lt;/p&gt;
&lt;p&gt;The core of the issue is that while the *values* of this array are processed, the *keys* are trusted implicitly and are not sanitized or validated.&lt;/p&gt;
&lt;p&gt;**File:** `src/phpMyFAQ/Controller/Administration/ConfigurationTabController.php`
```php
// ...
public function save(Request $request): JsonResponse
{
    $this-&amp;gt;userHasPermission(PermissionType::CONFIGURATION_EDIT);&lt;/p&gt;
&lt;p&gt;$configurationData = $request-&amp;gt;get(&amp;#39;edit&amp;#39;);
    // ...
    
    foreach ($configurationData as $key =&amp;gt; $value) {
        // The key from the user input is used to build the $newConfigValues array.
        $newConfigValues[$key] = (string) $value;
        // ...
    }&lt;/p&gt;
&lt;p&gt;// ...
    // The array, containing user-controlled keys, is passed to the model.
    $this-…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: thorsten/phpmyfaq, Packagist: phpmyfaq/phpmyfaq&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;An authenticated SQL injection vulnerability in the main configuration update functionality of phpMyFAQ (v4.0.13 and prior) allows a privileged user with &amp;#39;Configuration Edit&amp;#39; permissions to execute arbitrary SQL commands. Successful exploitation can lead to a full compromise of the database, including reading, modifying, or deleting all data, as well as potential remote code execution depending on the database configuration.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability exists in the `save` method within the `src/phpMyFAQ/Controller/Administration/ConfigurationTabController.php` controller. This method handles the saving of application-wide configuration settings. It retrieves all submitted form data as an associative array via `$request-&amp;gt;get(&amp;#39;edit&amp;#39;)`.&lt;/p&gt;
&lt;p&gt;The core of the issue is that while the *values* of this array are processed, the *keys* are trusted implicitly and are not sanitized or validated.&lt;/p&gt;
&lt;p&gt;**File:** `src/phpMyFAQ/Controller/Administration/ConfigurationTabController.php`
```php
// ...
public function save(Request $request): JsonResponse
{
    $this-&amp;gt;userHasPermission(PermissionType::CONFIGURATION_EDIT);&lt;/p&gt;
&lt;p&gt;$configurationData = $request-&amp;gt;get(&amp;#39;edit&amp;#39;);
    // ...
    
    foreach ($configurationData as $key =&amp;gt; $value) {
        // The key from the user input is used to build the $newConfigValues array.
        $newConfigValues[$key] = (string) $value;
        // ...
    }&lt;/p&gt;
&lt;p&gt;// ...
    // The array, containing user-controlled keys, is passed to the model.
    $this-…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fxm2-cmwj-qvx4</guid>
    </item>
  </channel>
</rss>
