Summaryinfo

A vulnerability, which was classified as critical, has been found in Redaxscript up to 2.2.x. This affects the function search_post of the file includes/search.php of the component Search. The manipulation of the argument search_terms leads to sql injection. This vulnerability is traded as CVE-2015-1518. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Redaxscript up to 2.2.x. It has been rated as critical. This issue affects the function search_post of the file includes/search.php of the component Search. The manipulation of the argument search_terms 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. The summary by CVE is:

SQL injection vulnerability in the search_post function in includes/search.php in Redaxscript before 2.3.0 allows remote attackers to execute arbitrary SQL commands via the search_terms parameter.

The weakness was shared 02/11/2015 as not defined posting (Bugtraq). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2015-1518 since 02/06/2015. 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 attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The exploit is available at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:includes/search.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 2.2.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Exploit-DB (36023). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Redaxscript

Version

• 2.0
• 2.1
• 2.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

Video

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion