| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in QwikiWiki. Impacted is an unknown function of the file pageindex.php. The manipulation of the argument help leads to cross site scripting. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability was found in QwikiWiki (Content Management System) (affected version not known) and classified as problematic. This issue affects some unknown functionality of the file pageindex.php. The manipulation of the argument help 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 released 03/09/2006 by Kiki (Website). The advisory is shared at kiki91.altervista.org. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details as well as a exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
After before and not just, there has been an exploit disclosed. It is declared as proof-of-concept. By approaching the search of inurl:pageindex.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 (25128), SecurityFocus (BID 17064†), OSVDB (23788†) and Secunia (SA19182†). Entries connected to this vulnerability are available at VDB-29164, VDB-83560 and VDB-83562. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.3
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: 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/09/2006 🔍03/09/2006 🔍
03/10/2006 🔍
03/10/2006 🔍
05/05/2016 🔍
11/16/2018 🔍
Sources
Advisory: kiki91.altervista.orgResearcher: Kiki
Status: Not defined
GCVE (VulDB): GCVE-100-83561
X-Force: 25128
SecurityFocus: 17064 - QwikiWiki Multiple Cross-Site Scripting Vulnerabilities
Secunia: 19182
OSVDB: 23788 - QwikiWiki pageindex.php help Parameter XSS
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/05/2016 22:16Updated: 11/16/2018 09:19
Changes: 05/05/2016 22:16 (47), 11/16/2018 09:19 (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.