Mywebland MyEvent 1.6 includes/template.php myevent_path file inclusion ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Mywebland MyEvent 1.6. This impacts an unknown function of the file includes/template.php. Executing a manipulation of the argument myevent_path can lead to file inclusion. This vulnerability is registered as CVE-2007-3353. No exploit is available. There is ongoing doubt regarding the real existence of this vulnerability.
Details
A vulnerability was found in Mywebland MyEvent 1.6. It has been declared as critical. This vulnerability affects an unknown code block of the file includes/template.php. The manipulation of the argument myevent_path with an unknown input leads to a file inclusion vulnerability. The CWE definition for the vulnerability is CWE-73. The product allows user input to control or influence paths or file names that are used in filesystem operations. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
** DISPUTED ** PHP remote file inclusion vulnerability in includes/template.php in MyEvent 1.6 allows remote attackers to execute arbitrary PHP code via a URL in the myevent_path parameter. NOTE: a reliable third party disputes this issue, saying "the entire file is a class."
The weakness was published 06/02/2007 by Yaser as not defined posting (Bugtraq). The advisory is shared for download at securityfocus.com. This vulnerability was named CVE-2007-3353 since 06/22/2007. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
The real existence of this vulnerability is still doubted at the moment. By approaching the search of inurl:includes/template.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 vulnerability database at OSVDB (36230†). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: File inclusionCWE: CWE-73
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
06/02/2007 🔍06/22/2007 🔍
06/22/2007 🔍
07/25/2007 🔍
03/15/2015 🔍
08/08/2024 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Yaser
Status: Not defined
Disputed: 🔍
CVE: CVE-2007-3353 (🔍)
GCVE (CVE): GCVE-0-2007-3353
GCVE (VulDB): GCVE-100-37420
OSVDB: 36230 - MyEvent includes/template.php myevent_path Parameter Remote File Inclusion
Entry
Created: 03/15/2015 15:58Updated: 08/08/2024 13:52
Changes: 03/15/2015 15:58 (45), 08/12/2017 10:42 (8), 08/08/2024 13:52 (17)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.