| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in phpProfiles and classified as critical. This affects an unknown function of the file upload_ht.inc.php. This manipulation of the argument usrinc causes privileges management. The identification of this vulnerability is CVE-2006-5634. Furthermore, there is an exploit available.
Details
A vulnerability has been found in phpProfiles (the affected version unknown) and classified as critical. Affected by this vulnerability is an unknown part of the file upload_ht.inc.php. The manipulation of the argument usrinc 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, integrity, and availability.
The weakness was shared 10/30/2006 by v1per-haCker (Website). The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2006-5634. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
A public exploit has been developed by v1per-haCker and been published even before and not after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:upload_ht.inc.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (29900), Exploit-DB (2688), SecurityFocus (BID 20819†), OSVDB (30138†) and Secunia (SA22644†). The entries VDB-33056 and VDB-84828 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: v1per-haCker
Download: 🔍
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/30/2006 🔍10/30/2006 🔍
10/30/2006 🔍
10/30/2006 🔍
10/31/2006 🔍
10/31/2006 🔍
05/08/2016 🔍
08/04/2024 🔍
Sources
Advisory: exploit-db.comResearcher: v1per-haCker
Status: Confirmed
CVE: CVE-2006-5634 (🔍)
GCVE (CVE): GCVE-0-2006-5634
GCVE (VulDB): GCVE-100-84829
X-Force: 29900
SecurityFocus: 20819 - PHPProfiles Reqpath Parameter Multiple Remote File Include Vulnerabilities
Secunia: 22644
OSVDB: 30138 - phpProfiles upload_ht.inc.php usrinc Parameter Remote File Inclusion
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/08/2016 20:07Updated: 08/04/2024 13:34
Changes: 05/08/2016 20:07 (50), 11/28/2018 13:26 (4), 08/06/2022 02:10 (3), 08/06/2022 02:18 (7), 08/04/2024 13:34 (16)
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.