Security readout for executives and security teams
Plain-English summary
Kimai 0.9.2.x has an unauthenticated SQL injection in db_restore.php. If an exposed instance runs with permissive database and web-directory conditions, an attacker could move from database injection to remote code execution. Treat internet-facing legacy Kimai 0.9.2 deployments as urgent.
Executive priority
Prioritize within the current emergency remediation queue if Kimai 0.9.2.x is deployed, especially if internet-facing. The business risk is full application compromise under documented environmental conditions, with public exploit material available.
Technical view
The issue is CWE-89 SQL injection through the dates[] POST parameter on db_restore.php. Sources describe arbitrary SQL injection and possible INTO OUTFILE file write under specific environmental conditions, enabling PHP payload placement in a web-accessible temporary directory. Confirmed affected builds include 0.9.2.beta, 0.9.2.1294.beta, 0.9.2.1306-3, and 0.9.2.0.
Likely exposure
Exposure is most likely in old self-hosted Kimai 0.9.2.x installations with db_restore.php reachable over the network. Risk increases where the database account can write files and the temporary directory is web-accessible.
Exploitation context
The bundle includes public exploit references from Metasploit, Exploit-DB, Vulners, and VulnCheck. The bundle does not indicate CISA KEV listing or confirmed active exploitation, so active exploitation should not be assumed from these sources alone.
Researcher notes
Evidence supports critical severity, unauthenticated reachability, and an RCE path dependent on database file-write capability and web-accessible PHP execution. Patch details are not provided in the supplied bundle; avoid asserting a fixed release without vendor confirmation.
Mitigation direction
- Identify and retire or upgrade Kimai 0.9.2.x instances.
- Check Kimai or vendor guidance for the supported fixed version.
- Block public access to db_restore.php and legacy admin surfaces.
- Remove unnecessary database FILE privileges from Kimai database users.
- Ensure temporary directories are not web-accessible or PHP-executable.
- Review web and database logs for suspicious db_restore.php access.
Validation and detection
- Inventory internet-facing and internal Kimai deployments by version.
- Confirm whether db_restore.php is reachable without authentication.
- Verify database users cannot write files through SQL.
- Check whether writable directories can execute PHP through the web server.
- Review logs around dates[] requests and restore activity.
- Validate remediation with unit, regression, documentation, and inline-comment review as applicable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2013-10033 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/unix/webapp/kimai_sqli.rbCVE reference · exploit
- https://www.exploit-db.com/exploits/30010CVE reference · exploit
- https://www.exploit-db.com/exploits/25606CVE reference · exploit
- https://vulners.com/metasploit/MSF:EXPLOIT-UNIX-WEBAPP-KIMAI_SQLI-CVE reference · exploit
- https://www.vulncheck.com/advisories/kimai-sqliCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.