LokiCMS up to 0.3.3 admin.php default code injection

Summaryinfo

A vulnerability identified as critical has been detected in LokiCMS up to 0.3.3. The affected element is an unknown function of the file admin.php. This manipulation of the argument default causes code injection. This vulnerability is tracked as CVE-2008-1860. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in LokiCMS up to 0.3.3 (Content Management System). It has been declared as very critical. Affected by this vulnerability is some unknown functionality of the file admin.php. The manipulation of the argument default with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Static code injection vulnerability in admin.php in LokiCMS 0.3.3 and earlier allows remote attackers to inject arbitrary PHP code into includes/Config.php via the default parameter.

The weakness was disclosed 04/17/2008 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2008-1860 since 04/17/2008. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/20/2024). MITRE ATT&CK project uses the attack technique T1059 for this issue.

It is possible to download the exploit at exploit-db.com. It is declared as functional. By approaching the search of inurl:admin.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 (41736), Exploit-DB (5408) and Secunia (SA29749†). The entries VDB-44635 and VDB-47573 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Content Management System

Name

• LokiCMS

Version

• 0.1.0
• 0.1.0rc1
• 0.2.0
• 0.3.0
• 0.3.1b1
• 0.3.1b2
• 0.3.2b1
• 0.3.3

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion