CVE-2010-0122
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 · uneditedMultiple SQL injection vulnerabilities in Employee Timeclock Software 0.99 allow remote attackers to execute arbitrary SQL commands via the (1) username or (2) password parameter to (a) auth.php or (b) login_action.php.
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 confidenceMultiple SQL injection vulnerabilities exist in the Employee Timeclock Software 0.99 authentication functionality. The username and password parameters in auth.php and login_action.php accept unsanitized user input that is directly concatenated into SQL queries, allowing remote attackers to inject arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.99CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 if Employee Timeclock Software is installedSearch for the software installation directory, typically in web root paths such as /var/www/, /htdocs/, or C:\inetpub\wwwroot\. Look for files named auth.php or login_action.php, or directories containing 'timeclock' or 'employee' in the name.Affected if The software version equals 0.99
-
Verify the affected version numberLocate any version file, readme, or configuration file within the timeclock installation directory. Compare the version to 0.99.Affected if Installed version is exactly 0.99
-
Confirm presence of vulnerable auth.php fileCheck for the existence of auth.php in the web-accessible directory. Inspect the file content for SQL query construction using username or password variables directly in the query string.Affected if auth.php exists and contains unsanitized SQL concatenation with username or password parameters
-
Confirm presence of vulnerable login_action.php fileCheck for the existence of login_action.php in the web-accessible directory. Inspect the file content for SQL query construction using username or password variables directly concatenated into queries.Affected if login_action.php exists and contains unsanitized SQL concatenation with username or password parameters
-
Verify authentication functionality is accessibleConfirm the login page is accessible via HTTP/HTTPS. Try accessing the login endpoint directly to determine if the authentication module is exposed and usable.Affected if The login page or authentication endpoints are reachable over the network
A user is affected if Employee Timeclock Software version 0.99 is installed and the auth.php or login_action.php files contain direct SQL concatenation with username or password parameters without prepared statements or input sanitization.
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 dataReplace dynamic SQL query construction with parameterized queries (prepared statements) in both auth.php and login_action.php for username and password parameters. Apply input validation as an additional defense layer.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0122 — 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-2010-0122 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