Particle Soft Particle Whois 1.0.3 index.php target cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Particle Soft Particle Whois 1.0.3. This impacts an unknown function of the file index.php. Executing a manipulation of the argument target can lead to cross site scripting. The identification of this vulnerability is CVE-2006-2965. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability classified as problematic was found in Particle Soft Particle Whois 1.0.3. This vulnerability affects an unknown part of the file index.php. The manipulation of the argument target with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. CVE summarizes:
Multiple cross-site scripting (XSS) vulnerabilities in Particle Soft Particle Whois 1.0.3 allow remote attackers to inject arbitrary web script or HTML via (1) the target parameter in index.php and (2) the "input box."
The weakness was shared 06/12/2006 by luny (Website). The advisory is available at vupen.com. This vulnerability was named CVE-2006-2965 since 06/12/2006. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
It is declared as proof-of-concept. By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.
The vulnerability is also documented in the databases at X-Force (26954), SecurityFocus (BID 18346†) and Secunia (SA20490†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.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: 🔍
NVD Base Score: 🔍
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: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
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
05/25/2006 🔍06/07/2006 🔍
06/12/2006 🔍
06/12/2006 🔍
06/12/2006 🔍
03/12/2015 🔍
09/18/2017 🔍
Sources
Advisory: vupen.com⛔Researcher: luny
Status: Confirmed
CVE: CVE-2006-2965 (🔍)
GCVE (CVE): GCVE-0-2006-2965
GCVE (VulDB): GCVE-100-30754
X-Force: 26954 - Particle Whois index.php \
SecurityFocus: 18346 - Particle Whois Multiple Input Validation Vulnerabilities
Secunia: 20490 - Particle Whois "target" Parameter Cross-Site Scripting, Less Critical
Vupen: ADV-2006-2168
Entry
Created: 03/12/2015 14:25Updated: 09/18/2017 11:35
Changes: 03/12/2015 14:25 (57), 09/18/2017 11:35 (3)
Complete: 🔍
Cache ID: 216:8E7:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.