Cyclope-Series Cyclope Employee Surveillance Solution 6.x Username sql injection

Summaryinfo

A vulnerability was found in Cyclope-Series Cyclope Employee Surveillance Solution 6.x. It has been rated as critical. This affects an unknown part. The manipulation of the argument Username leads to sql injection. This vulnerability is uniquely identified as CVE-2012-10047. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Cyclope-Series Cyclope Employee Surveillance Solution 6.x. This issue affects an unknown function. The manipulation of the argument username 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:

Cyclope Employee Surveillance Solution versions 6.x are vulnerable to a SQL injection flaw in its login mechanism. The username parameter in the auth-login POST request is not properly sanitized, allowing attackers to inject arbitrary SQL statements. This can be leveraged to write and execute a malicious PHP file on disk, resulting in remote code execution under the SYSTEM user context.

The weakness was disclosed by loneferret. The advisory is shared at raw.githubusercontent.com. The identification of this vulnerability is CVE-2012-10047 since 08/08/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. MITRE ATT&CK project uses the attack technique T1505 for this issue.

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 (20393) and EUVD (EUVD-2012-6589). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Cyclope-Series

Name

• Cyclope Employee Surveillance Solution

Version

• 6.x

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