# CVE-2020-37005: TimeClock Software 1.01 Authenticated Time-Based SQL Injection

> Authenticated attackers can enumerate valid usernames via time-based SQL injection in the notes parameter of add_entry.php.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-hfq2-v7vg-r2m2

## What is CVE-2020-37005?

CVE-2020-37005 is a high-severity SQL injection vulnerability in TimeClock Software, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TimeClock Software 1.01 contains an authenticated time-based SQL injection vulnerability that allows attackers to enumerate valid usernames by manipulating the 'notes' parameter. Attackers can inject conditional time delays in the add_entry.php endpoint to determine user existence by measuring response time differences.

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

## Which versions are affected by CVE-2020-37005?


## How do I fix CVE-2020-37005?

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

## Is CVE-2020-37005 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37005 and fix it if it is affected.

What it is: CVE-2020-37005 is a high-severity SQL injection vulnerability in TimeClock Software, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37005 exists.

Affected product: TimeClock Software. 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-2020-37005/ (Markdown: https://insights.sbomify.com/CVE-2020-37005/index.md)
```

## Sources

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

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