CVE-2012-10047
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCyclope 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCyclope Employee Surveillance Solution v6.x contains a SQL injection vulnerability in the username parameter of the auth-login POST request. Attackers can inject arbitrary SQL statements through this unsanitized input, which can be leveraged to write a malicious PHP file to disk and achieve remote code execution under SYSTEM context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Cyclope Employee Surveillance Solution installationLocate the Cyclope installation directory or check running web services for Cyclope application files. Look for the main application directory typically named 'cyclope' or check IIS/Apache/nginx vhost configurations pointing to Cyclope.Affected if Cyclope Employee Surveillance Solution is installed and the version is 6.x (any minor version).
-
Determine installed version numberCheck the application's version file, about page, or footer for the version number. If source code is accessible, examine version.php, version.txt, or similar version metadata files in the installation root.Affected if The version begins with 6 (e.g., 6.0, 6.1, 6.2, 6.x). Earlier versions like 5.x are not affected by this specific CVE.
-
Verify login functionality is exposedConfirm the auth-login endpoint is accessible by accessing the login page URL (typically /auth-login or /login on the Cyclope web interface). Use a web browser or curl to request the endpoint.Affected if The login page at /auth-login (or similar) is accessible and accepts POST requests to the same endpoint.
-
Confirm vulnerable parameter existsExamine the login form HTML source or capture the HTTP request when submitting the form. Verify that a 'username' parameter is submitted via POST to the auth-login handler.Affected if The login form contains a username input field and submits to the auth-login POST endpoint without visible input sanitization or parameterized query handling in the backend code.
A system is affected if Cyclope Employee Surveillance Solution version 6.x is installed and the web-based login interface (auth-login endpoint) is accessible and uses unparameterized SQL queries for the username field.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries or prepared statements for all user inputs in the login mechanism to prevent SQL injection. Additionally, apply the principle of least privilege to the database user and validate/sanitize all inputs.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-10047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-10047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data