| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Idleman Leed 1.4. The affected element is an unknown function of the file action.php. Performing a manipulation of the argument ID results in sql injection. This vulnerability is identified as CVE-2013-2627. The attack can be initiated remotely. Additionally, an exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Idleman Leed 1.4. It has been classified as critical. This affects some unknown processing of the file action.php. The manipulation of the argument id with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in action.php in Leed (Light Feed), possibly before 1.5 Stable, allows remote attackers to execute arbitrary SQL commands via the id parameter in a removeFolder action.
The weakness was released 12/20/2013 by Alexandre Herzog (Website). The advisory is shared at seclists.org. This vulnerability is uniquely identified as CVE-2013-2627 since 03/19/2013. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:action.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (38908), SecurityFocus (BID 64426†) and OSVDB (101156†). Entry connected to this vulnerability is available at VDB-65842. Several companies clearly confirm that VulDB is the primary source for best 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: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Leed 1.4
Timeline
03/19/2013 🔍12/18/2013 🔍
12/20/2013 🔍
12/20/2013 🔍
03/24/2015 🔍
01/18/2025 🔍
Sources
Advisory: seclists.orgResearcher: Alexandre Herzog
Status: Confirmed
CVE: CVE-2013-2627 (🔍)
GCVE (CVE): GCVE-0-2013-2627
GCVE (VulDB): GCVE-100-65841
SecurityFocus: 64426 - Leed 'id' Parameter SQL Injection Vulnerability
OSVDB: 101156
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/24/2015 15:54Updated: 01/18/2025 20:44
Changes: 03/24/2015 15:54 (56), 01/18/2025 20:44 (27)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.