| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in phpMyFAQ 2.8.2. It has been rated as critical. This affects an unknown function of the file ajaxfilemanager.php. This manipulation causes privileges management. Furthermore, an exploit is available. Upgrading the affected component is advised.
Details
A vulnerability classified as critical was found in phpMyFAQ 2.8.2 (Content Management System). Affected by this vulnerability is an unknown function of the file ajaxfilemanager.php. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, and integrity.
The weakness was published 11/16/2013 by DevilSreaM as not defined posting (Pastebin). The advisory is shared at pastebin.com. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation requires a single authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
After immediately, there has been an exploit disclosed. It is declared as proof-of-concept. By approaching the search of inurl:ajaxfilemanager.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.8.3 eliminates this vulnerability. A possible mitigation has been published 2 days after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (100244†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.4
VulDB Temp Score: 4.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Google Hack: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍
Upgrade: phpMyFAQ 2.8.3
Timeline
11/16/2013 🔍11/16/2013 🔍
11/18/2013 🔍
11/28/2013 🔍
03/23/2019 🔍
Sources
Advisory: pastebin.comResearcher: DevilSreaM
Status: Not defined
GCVE (VulDB): GCVE-100-11305
OSVDB: 100244
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/28/2013 11:13Updated: 03/23/2019 11:41
Changes: 11/28/2013 11:13 (47), 03/23/2019 11:41 (2)
Complete: 🔍
Committer: olku
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.