Summary
Kimai leaks API Token Hash via Invoice Twig Template
Impact
An admin can silently embed token-exfiltration code in a shared invoice template. Every user who subsequently generates an invoice using that template will have their hashed API token leaked into the invoice output.
- API passwords are deprecated since April 2024 and not in wide use anymore (especially by new users)
- The function
getPlainApiToken()does NEVER return any data - The function
getApiToken()might return a bcrypt or sodium hashed API password, if the user (who created the invoice) has configured one - this cannot be used, but needs to be cracked using rainbow tables - The cloud does not allow Twig template upload, this is only relevant for OnPremise installations with template upload activated
GHSA-RH42-6RJ2-XWMC has a CVSS score of 2.0 (Low). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.53.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
The SecurityPolicy was changed to exclude methods that contains certain trigger words instead of using the hard-coded list, see https://github.com/kimai/kimai/pull/5878
This disables access to both the getApiToken() and getPlainApiToken() function.
Frequently Asked Questions
- What is GHSA-RH42-6RJ2-XWMC? GHSA-RH42-6RJ2-XWMC is a low-severity security vulnerability in kimai/kimai (composer), affecting versions <= 2.52.0. It is fixed in 2.53.0.
- How severe is GHSA-RH42-6RJ2-XWMC? GHSA-RH42-6RJ2-XWMC has a CVSS score of 2.0 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of kimai/kimai are affected by GHSA-RH42-6RJ2-XWMC? kimai/kimai (composer) versions <= 2.52.0 is affected.
- Is there a fix for GHSA-RH42-6RJ2-XWMC? Yes. GHSA-RH42-6RJ2-XWMC is fixed in 2.53.0. Upgrade to this version or later.
- Is GHSA-RH42-6RJ2-XWMC exploitable, and should I be worried? Whether GHSA-RH42-6RJ2-XWMC is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-RH42-6RJ2-XWMC is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-RH42-6RJ2-XWMC? Upgrade
kimai/kimaito 2.53.0 or later.