thorsten phpMyFAQ up to 3.2.4 Echo attachments.php filename cross site scripting

Summaryinfo

A vulnerability, which was classified as problematic, has been found in thorsten phpMyFAQ up to 3.2.4. Affected by this issue is some unknown functionality of the file phpMyFAQ\phpmyfaq\admin\attachments.php of the component Echo Handler. The manipulation of the argument filename leads to cross site scripting. This vulnerability is traded as CVE-2024-24574. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in thorsten phpMyFAQ up to 3.2.4 (Content Management System) and classified as problematic. This issue affects an unknown functionality of the file phpMyFAQ\phpmyfaq\admin\attachments.php of the component Echo Handler. The manipulation of the argument filename with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

phpMyFAQ is an open source FAQ web application for PHP 8.1+ and MySQL, PostgreSQL and other databases. Unsafe echo of filename in phpMyFAQ\phpmyfaq\admin\attachments.php leads to allowed execution of JavaScript code in client side (XSS). This vulnerability has been patched in version 3.2.5.

The weakness was shared 02/06/2024 as GHSA-7m8g-fprr-47fx. The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-24574 since 01/25/2024. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

By approaching the search of inurl:phpMyFAQ\phpmyfaq\admin\attachments.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 3.2.5 eliminates this vulnerability. Applying the patch 5479b4a4603cce71aa7eb4437f1c201153a1f1f5 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Vendor

• thorsten

Name

• phpMyFAQ

Version

• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4

License

• open-source

Website

• Product: https://github.com/thorsten/phpMyFAQ/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion