Kimai 0.9.2.x db_restore.php dates sql injection

Summaryinfo

A vulnerability was found in Kimai 0.9.2.x. It has been classified as critical. This issue affects some unknown processing of the file db_restore.php. This manipulation of the argument dates causes sql injection. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is handled as CVE-2013-10033. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability classified as critical was found in Kimai 0.9.2.x. Affected by this vulnerability is an unknown code block of the file db_restore.php. The manipulation of the argument dates with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was released by drone. The advisory is shared at raw.githubusercontent.com. This vulnerability is known as CVE-2013-10033 since 07/30/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:db_restore.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Exploit-DB (25606) and EUVD (EUVD-2013-7255). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Kimai

Version

• 0.9.2.x

Support

• end of life

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion