phpMyFAQ up to 2.8.12 Restore sql injection

Summaryinfo

A vulnerability classified as critical has been found in phpMyFAQ up to 2.8.12. This impacts an unknown function of the component Restore. Performing a manipulation results in sql injection. This vulnerability is reported as CVE-2014-6045. The attack is possible to be carried out remotely. Moreover, an exploit is present. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in phpMyFAQ up to 2.8.12 (Content Management System). It has been classified as critical. This affects some unknown processing of the component Restore. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to execute arbitrary SQL commands via vectors involving the restore function.

The bug was discovered 09/16/2014. The weakness was disclosed 08/28/2018 (Website). The advisory is shared at phpmyfaq.de. This vulnerability is uniquely identified as CVE-2014-6045 since 09/01/2014. The exploitability is told to be easy. It is possible to initiate the attack remotely. Required for exploitation is a authentication. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1442 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 2.8.13 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Exploit-DB (34580). The entries VDB-123298, VDB-123299, VDB-123300 and VDB-123301 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Name

• phpMyFAQ

Version

• 2.8.0
• 2.8.1
• 2.8.2
• 2.8.3
• 2.8.4
• 2.8.5
• 2.8.6
• 2.8.7
• 2.8.8
• 2.8.9
• 2.8.10
• 2.8.11
• 2.8.12

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion