SITEMAKIN SLAC 1.0 users.php my_item_search sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in SITEMAKIN SLAC 1.0. This issue affects some unknown processing of the file users.php. Performing a manipulation of the argument my_item_search as part of Parameter results in sql injection. This vulnerability is reported as CVE-2018-11535. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as critical has been found in SITEMAKIN SLAC 1.0. This affects an unknown functionality of the file users.php. The manipulation of the argument my_item_search as part of a Parameter 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:

An issue was discovered in SITEMAKIN SLAC (Site Login and Access Control) v1.0. The parameter "my_item_search" in users.php is exploitable using SQL injection.

The bug was discovered 05/23/2018. The weakness was disclosed 05/29/2018 (Website). It is possible to read the advisory at gist.github.com. This vulnerability is uniquely identified as CVE-2018-11535 since 05/29/2018. 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. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:users.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 vulnerability database at Exploit-DB (44793). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• SITEMAKIN

Name

• SLAC

Version

• 1.0

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion