| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Indexu. It has been classified as problematic. Affected by this issue is some unknown functionality of the file user_detail.php. The manipulation of the argument u leads to cross site scripting. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in Indexu (Content Management System) (unknown version). This issue affects an unknown code block of the file user_detail.php. The manipulation of the argument u with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Impacted is integrity.
The weakness was disclosed 01/16/2007 by ViP HaCkEr (AL-garnei) (Website). The advisory is shared at archives.neohapsis.com. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
After immediately, there has been an exploit disclosed. By approaching the search of inurl:user_detail.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 (31538), SecurityFocus (BID 22084†), OSVDB (32841†) and Secunia (SA23764†). The entries VDB-34511, VDB-85095, VDB-85096 and VDB-85098 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
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: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
01/16/2007 🔍01/16/2007 🔍
01/16/2007 🔍
01/17/2007 🔍
01/17/2007 🔍
05/08/2016 🔍
12/17/2018 🔍
Sources
Advisory: archives.neohapsis.comResearcher: ViP HaCkEr (AL-garnei)
Status: Not defined
GCVE (VulDB): GCVE-100-85097
X-Force: 31538
SecurityFocus: 22084 - IndexU Multiple Cross-Site Scripting Vulnerabilities
Secunia: 23764 - Indexu Multiple Cross-Site Scripting Vulnerabilities, Less Critical
OSVDB: 32841 - Indexu user_detail.php u Parameter XSS
See also: 🔍
Entry
Created: 05/08/2016 21:40Updated: 12/17/2018 08:20
Changes: 05/08/2016 21:40 (50), 12/17/2018 08:20 (2)
Complete: 🔍
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.