| 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 myBloggie. This vulnerability affects unknown code of the file deluser.php. The manipulation of the argument ID leads to cross site scripting. The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in myBloggie (affected version not known). This issue affects some unknown functionality of the file deluser.php. The manipulation of the argument id 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 presented 03/09/2006 by Nenad Jovanovic (Website). It is possible to read the advisory at seclab.tuwien.ac.at. 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. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
After before and not just, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:deluser.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 SecurityFocus (BID 17048†) and OSVDB (23975†). See VDB-29173, VDB-83602, VDB-83609 and VDB-83610 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
License
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/09/2006 🔍
03/18/2006 🔍
05/06/2016 🔍
11/17/2018 🔍
Sources
Advisory: seclab.tuwien.ac.atResearcher: Nenad Jovanovic
Status: Not defined
GCVE (VulDB): GCVE-100-83603
SecurityFocus: 17048 - MyBloggie Multiple Cross-Site Scripting Vulnerabilities
OSVDB: 23975 - myBloggie deluser.php 'id' Parameter XSS
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/06/2016 08:12Updated: 11/17/2018 09:50
Changes: 05/06/2016 08:12 (45), 11/17/2018 09:50 (2)
Complete: 🔍
Cache ID: 216:B7E:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.