Gxlcms QY 1.0.0713 DataAction.class.php upsql sql injection

Summaryinfo

A vulnerability was found in Gxlcms QY 1.0.0713. It has been rated as critical. Affected is the function upsql of the file Lib\Lib\Action\Admin\DataAction.class.php. This manipulation of the argument sql as part of Parameter causes sql injection. This vulnerability is registered as CVE-2018-9247. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Gxlcms QY 1.0.0713. It has been declared as critical. Affected by this vulnerability is the function upsql of the file Lib\Lib\Action\Admin\DataAction.class.php. The manipulation of the argument sql as part of a Parameter leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The upsql function in \Lib\Lib\Action\Admin\DataAction.class.php in Gxlcms QY v1.0.0713 allows remote attackers to execute arbitrary SQL statements via the sql parameter. Consequently, an attacker can execute arbitrary PHP code by placing it after a <?php substring, and then using INTO OUTFILE with a .php filename.

The bug was discovered 04/03/2018. The weakness was published 04/04/2018 (Website). It is possible to read the advisory at atksec.com. This vulnerability is known as CVE-2018-9247 since 04/03/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

By approaching the search of inurl:Lib\Lib\Action\Admin\DataAction.class.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.

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

Productinfo

Name

• Gxlcms QY

Version

• 1.0.0713

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