| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in phpMyFAQ up to 2.8.12. Affected by this vulnerability is an unknown functionality of the component Permission Check. The manipulation leads to permission. This vulnerability is traded as CVE-2014-6047. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in phpMyFAQ up to 2.8.12 (Content Management System). It has been rated as critical. This issue affects an unknown functionality of the component Permission Check. The manipulation with an unknown input leads to a permission vulnerability. Using CWE to declare the problem leads to CWE-275. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to read arbitrary attachments by leveraging incorrect "download an attachment" permission checks.
The bug was discovered 09/16/2014. The weakness was shared 08/28/2018 (Website). It is possible to read the advisory at phpmyfaq.de. The identification of this vulnerability is CVE-2014-6047 since 09/01/2014. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Technical details are unknown but a public exploit is available. The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.
The exploit is available 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-123297, VDB-123298, VDB-123300 and VDB-123301 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.5
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: PermissionCWE: CWE-275 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: phpMyFAQ 2.8.13
Timeline
09/01/2014 🔍09/16/2014 🔍
08/28/2018 🔍
08/28/2018 🔍
08/29/2018 🔍
03/28/2025 🔍
Sources
Advisory: phpmyfaq.deStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2014-6047 (🔍)
GCVE (CVE): GCVE-0-2014-6047
GCVE (VulDB): GCVE-100-123299
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 08/29/2018 07:00Updated: 03/28/2025 11:17
Changes: 08/29/2018 07:00 (59), 03/18/2020 16:09 (2), 03/28/2025 11:17 (26)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.