phpMyFAQ up to 2.8.12 Authorization Parameter improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in phpMyFAQ up to 2.8.12 and classified as critical. This affects an unknown part of the component Authorization. This manipulation as part of Parameter causes improper authorization. This vulnerability is handled as CVE-2014-6049. The attack can be initiated remotely. Additionally, an exploit exists. The affected component should be upgraded.
Details
A vulnerability classified as critical was found in phpMyFAQ up to 2.8.12 (Content Management System). Affected by this vulnerability is an unknown part of the component Authorization. The manipulation as part of a Parameter leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
phpMyFAQ before 2.8.13 allows remote authenticated users with admin privileges to bypass authorization via a crafted instance ID parameter.
The bug was discovered 09/16/2014. The weakness was released 08/28/2018 (Website). The advisory is shared at phpmyfaq.de. This vulnerability is known as CVE-2014-6049 since 09/01/2014. The attack can be launched remotely. A single authentication is necessary for exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
It is possible to download the exploit 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). Entries connected to this vulnerability are available at VDB-123297, VDB-123298, VDB-123299 and VDB-123300. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.2
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 2.7
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: Improper authorizationCWE: CWE-285 / 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/26/2025 🔍
Sources
Advisory: phpmyfaq.deStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2014-6049 (🔍)
GCVE (CVE): GCVE-0-2014-6049
GCVE (VulDB): GCVE-100-123301
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 08/29/2018 07:01Updated: 03/26/2025 22:47
Changes: 08/29/2018 07:01 (60), 03/18/2020 16:25 (2), 03/26/2025 22:47 (26)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.