Kimai vulnerable to formula Injection via tag names in XLSX export
Summary
Any ROLE_USER can create a tag with a formula string as its name (e.g. =SUM(54+51)) via POST /api/tags and assign it to a timesheet. When an admin exports timesheets to XLSX, ArrayFormatter.formatValue() joins tag names with implode() and returns the result unchanged. OpenSpout promotes any =-prefixed string to a FormulaCell, writing <f>SUM(54+51)</f> into the XLSX archive. Excel evaluates the formula when the file is opened.
Details
1. ArrayFormatter does not sanitize before returning
sanitizeDDE() exists on StringHelper and is called by TextFormatter, but ArrayFormatter never calls it.
// src/Export/Package/CellFormatter/ArrayFormatter.php:24
return implode(', ', $value); // no sanitizeDDE() call
2. Tag name validation does not block formula trigger characters
The API blocks commas in tag names but permits =, +, -, and @ - all valid formula prefixes in Excel and LibreOffice Calc.
3. OpenSpout silently promotes strings to formula cells
Cell::fromValue("=SUM(54+51)") returns a FormulaCell with no warning.
PoC
- It logs in as normal user, creates tag
=SUM(54+51), assigns it to a timesheet. - Admin has to export timesheets to Excel version via
/en/export/endpoint.
Impact
- Any
ROLE_USERcan plant a formula that executes on the workstation of any user who exports and opens timesheet data - A single malicious tag poisons all future exports across all users and date ranges until the tag is deleted
Fixes
- Prevent
=being part of the tag name (and other fields as well) - Use OpenSpout
TextCellfor everything that is a string
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de Composer | kimai/kimai | >= 2.27.0, < 2.54.0 | 2.54.0 |
Referencias
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N- Debilidad (CWE)
CWE-1236- Plataforma
- Composer
- Paquete
kimai/kimai- Publicada
- 05.05.2026
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-3xc2-h5r3-wv3r - CC BY 4.0
Historial de vulnerabilidades: kimai/kimai
Todas las vulnerabilidades publicadas de este paquete (Paquete de Composer), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 33
- Primera → última
- 02.2023 07.2026
- Sin corrección
- 1
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 2
- Alta 4
- Media 20
- Baja 7
Divulgaciones por año
- 2023: 2
- 2024: 3
- 2025: 1
- 2026: 27
-
Kimai vulnerable to formula Injection via tag names in XLSX export esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.