| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Ublog Reload. The affected element is an unknown function of the file users.asp. Performing a manipulation results in cross site scripting. This vulnerability is known as CVE-2007-0798. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Ublog Reload (Blog Software) (version now known). It has been classified as problematic. This affects some unknown processing of the file users.asp. The manipulation 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 published 02/03/2007 (Website). The advisory is shared at hackerscenter.com. This vulnerability is uniquely identified as CVE-2007-0798 since 02/06/2007. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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.
By approaching the search of inurl:users.asp 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 (32185), SecurityFocus (BID 22382†) and OSVDB (33644†). Similar entries are available at VDB-34859, VDB-34858, VDB-85243 and VDB-85244. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: 🔍
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: Not defined
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
10/18/2006 🔍02/03/2007 🔍
02/06/2007 🔍
02/06/2007 🔍
02/25/2007 🔍
05/08/2016 🔍
08/09/2022 🔍
Sources
Advisory: hackerscenter.comStatus: Not defined
CVE: CVE-2007-0798 (🔍)
GCVE (CVE): GCVE-0-2007-0798
GCVE (VulDB): GCVE-100-85245
X-Force: 32185
SecurityFocus: 22382 - Ublog Reload HTML Injection and SQL Injection Vulnerabilities
OSVDB: 33644 - Ublog Reload users.asp Unspecified XSS
See also: 🔍
Entry
Created: 05/08/2016 21:45Updated: 08/09/2022 11:44
Changes: 05/08/2016 21:45 (51), 12/14/2018 10:10 (2), 08/09/2022 11:44 (3)
Complete: 🔍
Cache ID: 216:579: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.