| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Opial 1.0. This issue affects some unknown processing of the file home.php. The manipulation of the argument genres_parent results in cross site scripting. This vulnerability was named CVE-2009-3751. The attack may be performed from remote. In addition, an exploit is available.
Details
A vulnerability, which was classified as problematic, was found in Opial 1.0. Affected is an unknown code block of the file home.php. The manipulation of the argument genres_parent with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. CVE summarizes:
Cross-site scripting (XSS) vulnerability in home.php in Opial 1.0 allows remote attackers to inject arbitrary web script or HTML via the genres_parent parameter.
The weakness was presented 10/22/2009 (Website). The advisory is available at milw0rm.com. This vulnerability is traded as CVE-2009-3751 since 10/22/2009. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details and a public exploit are known. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:home.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 (51679), Exploit-DB (9122), SecurityFocus (BID 35641†) and Secunia (SA35677†). See VDB-48932, VDB-48889, VDB-48888 and VDB-50540 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
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-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/03/2009 🔍07/11/2009 🔍
10/22/2009 🔍
10/22/2009 🔍
10/22/2009 🔍
03/18/2015 🔍
12/03/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Not defined
CVE: CVE-2009-3751 (🔍)
GCVE (CVE): GCVE-0-2009-3751
GCVE (VulDB): GCVE-100-50538
X-Force: 51679
SecurityFocus: 35641 - Opial Multiple Vulnerabilities
Secunia: 35677 - Opial Multiple Vulnerabilities, Highly Critical
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/18/2015 15:15Updated: 12/03/2024 12:48
Changes: 03/18/2015 15:15 (56), 01/23/2019 08:09 (4), 12/03/2024 12:48 (21)
Complete: 🔍
Cache ID: 216::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.