# CVE-2010-0122: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via login parameters, potentially accessing or modifying database contents.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-855f-vpmx-8c43

## What is CVE-2010-0122?

CVE-2010-0122 is a high-severity SQL injection vulnerability in n/a, published on 12 Mar 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2010-0122?

It affects 1 product.


Products: Timeclock-Software Employee Timeclock Software.

## How do I fix CVE-2010-0122?

No fix has been published for CVE-2010-0122 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-0122 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0122 exists.

Public exploit code:

- Employee TimeClock Software 0.99 - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-0707](https://insights.sbomify.com/CVE-2010-0707/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2010-0123](https://insights.sbomify.com/CVE-2010-0123/): Information disclosure in n/a (medium 5.0)
- [CVE-2010-0124](https://insights.sbomify.com/CVE-2010-0124/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0122 and fix it if it is affected.

What it is: CVE-2010-0122 is a high-severity SQL injection vulnerability in n/a, published on 12 Mar 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0122 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-0122/ (Markdown: https://insights.sbomify.com/CVE-2010-0122/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-0122
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-0122
- OSV: https://osv.dev/vulnerability/CVE-2010-0122

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-0122/
Summaries are generated and may contain mistakes; the official description above is the record.