# CVE-2013-10033: Kimai 0.9.2 db_restore.php SQL Injection

> Unauthenticated attackers can inject SQL via db_restore.php to write PHP files, achieving remote code execution in Kimai time tracking software.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-ff3c-wfr9-cj43

## What is CVE-2013-10033?

CVE-2013-10033 is a critical SQL injection vulnerability in Kimai, published on 31 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated SQL injection vulnerability exists in Kimai version 0.9.2.x via the db_restore.php endpoint. The flaw allows attackers to inject arbitrary SQL queries into the dates[] POST parameter, enabling file write via INTO OUTFILE under specific environmental conditions. This can lead to remote code execution by writing a PHP payload to the web-accessible temporary directory. The vulnerability has been confirmed in versions including 0.9.2.beta, 0.9.2.1294.beta, and 0.9.2.1306-3.

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

## Which versions are affected by CVE-2013-10033?


## How do I fix CVE-2013-10033?

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

## Is CVE-2013-10033 being exploited?

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

Public exploit code:

- Kimai v0.9.2 'db_restore.php' SQL Injection (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-10033 and fix it if it is affected.

What it is: CVE-2013-10033 is a critical SQL injection vulnerability in Kimai, published on 31 Jul 2025. 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-2013-10033 exists.

Affected product: Kimai. 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-2013-10033/ (Markdown: https://insights.sbomify.com/CVE-2013-10033/index.md)
```

## Sources

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

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