thorsten phpMyFAQ up to 3.2.9 FAQ Record clickjacking

Summaryinfo

A vulnerability, which was classified as problematic, has been found in thorsten phpMyFAQ up to 3.2.9. The affected element is an unknown function of the component FAQ Record. Performing a manipulation results in clickjacking. This vulnerability is identified as CVE-2024-55889. The attack can be initiated remotely. Additionally, an exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in thorsten phpMyFAQ up to 3.2.9. This affects an unknown functionality of the component FAQ Record. The manipulation with an unknown input leads to a clickjacking vulnerability. CWE is classifying the issue as CWE-451. The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks. This is going to have an impact on integrity. The summary by CVE is:

phpMyFAQ is an open source FAQ web application. Prior to version 3.2.10, a vulnerability exists in the FAQ Record component where a privileged attacker can trigger a file download on a victim's machine upon page visit by embedding it in an element without user interaction or explicit consent. Version 3.2.10 fixes the issue.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-55889 since 12/12/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation needs additional levels of successful authentication. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1566.003 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.

Upgrading to version 3.2.10 eliminates this vulnerability. Applying the patch fa0f7368dc3288eedb1915def64ef8fb270f711d 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.

The vulnerability is also documented in the vulnerability database at Exploit-DB (52235). 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
• 3.2.5
• 3.2.6
• 3.2.7
• 3.2.8
• 3.2.9

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