| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Indexu. Impacted is an unknown function of the file search.php. Performing a manipulation of the argument keyword results in cross site scripting. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Indexu (Content Management System) (affected version not known). It has been classified as problematic. This affects some unknown functionality of the file search.php. The manipulation of the argument keyword with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity.
The weakness was released 01/16/2007 by ViP HaCkEr (AL-garnei) (Website). The advisory is shared at archives.neohapsis.com. It is possible to initiate the attack 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:search.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 (32845†) and Secunia (SA23764†). Entries connected to this vulnerability are available at VDB-34511, VDB-85095, VDB-85096 and VDB-85097. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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 🔍
05/08/2016 🔍
12/18/2018 🔍
Sources
Advisory: archives.neohapsis.comResearcher: ViP HaCkEr (AL-garnei)
Status: Not defined
GCVE (VulDB): GCVE-100-85101
X-Force: 31538
SecurityFocus: 22084 - IndexU Multiple Cross-Site Scripting Vulnerabilities
Secunia: 23764
OSVDB: 32845 - Indexu search.php keyword Parameter XSS
See also: 🔍
Entry
Created: 05/08/2016 21:40Updated: 12/18/2018 10:03
Changes: 05/08/2016 21:40 (48), 12/18/2018 10:03 (1)
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.