| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Enanocms up to 1.0.6. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file includes/comment.php. Such manipulation leads to sql injection. This vulnerability is uniquely identified as CVE-2010-0471. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Enanocms up to 1.0.6. It has been rated as critical. Affected by this issue is some unknown processing of the file includes/comment.php. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. CVE summarizes:
SQL injection vulnerability in the comment submission interface (includes/comment.php) in Enano CMS before 1.0.6pl1 allows remote attackers to execute arbitrary SQL commands via unspecified parameters.
The weakness was disclosed 08/24/2009 (Website). The advisory is available at enanocms.org. This vulnerability is handled as CVE-2010-0471 since 02/02/2010. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
By approaching the search of inurl:includes/comment.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.0.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at OSVDB (61974†) and Secunia (SA38253†). 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: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: Sql injectionCWE: CWE-89 / 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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Enanocms 1.0.1
Timeline
08/24/2009 🔍08/24/2009 🔍
01/28/2010 🔍
01/28/2010 🔍
02/02/2010 🔍
02/02/2010 🔍
03/18/2015 🔍
08/16/2017 🔍
Sources
Advisory: enanocms.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2010-0471 (🔍)
GCVE (CVE): GCVE-0-2010-0471
GCVE (VulDB): GCVE-100-51722
Secunia: 38253 - Enano CMS SQL Injection Vulnerability, Moderately Critical
OSVDB: 61974 - Enano CMS includes/comment.php Comment Submission Interface SQL Injection
Entry
Created: 03/18/2015 15:15Updated: 08/16/2017 04:13
Changes: 03/18/2015 15:15 (46), 08/16/2017 04:13 (10)
Complete: 🔍
Cache ID: 216:E3D: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.