InstantCMS up to 1.6 HTTP GET Request eval look eval injection

Summaryinfo

A vulnerability was found in InstantCMS up to 1.6. It has been rated as critical. This vulnerability affects the function eval of the component HTTP GET Request Handler. The manipulation of the argument look leads to eval injection. This vulnerability is listed as CVE-2013-10051. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in InstantCMS up to 1.6. It has been rated as critical. This issue affects the function eval of the component HTTP GET Request Handler. The manipulation of the argument look with an unknown input leads to a eval injection vulnerability. Using CWE to declare the problem leads to CWE-95. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval"). Impacted is confidentiality, integrity, and availability. The summary by CVE is:

A remote PHP code execution vulnerability exists in InstantCMS version 1.6 and earlier due to unsafe use of eval() within the search view handler. Specifically, user-supplied input passed via the look parameter is concatenated into a PHP expression and executed without proper sanitation. A remote attacker can exploit this flaw by sending a crafted HTTP GET request with a base64-encoded payload in the Cmd header, resulting in arbitrary PHP code execution within the context of the web server.

The weakness was presented by Ricardo Jorge Borges De Almeida. It is possible to read the advisory at raw.githubusercontent.com. The identification of this vulnerability is CVE-2013-10051 since 08/01/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.

The exploit is available at exploit-db.com. It is declared as proof-of-concept.

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 Exploit-DB (26622) and EUVD (EUVD-2013-7270). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• InstantCMS

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion