Is kevinpapst/kimai2 vulnerable?

Composer kevinpapst/kimai2 has 9 known advisories in the phpwarden feed. Feed 2026.10.29.4, updated 2026-10-29.

9advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2021-3985kimai2 is vulnerable to Cross-site Scriptinghigh8.0<1.16.31.16.3
CVE-2021-3992kimai2 is vulnerable to Improper Access Controlmedium6.5<1.16.31.16.3
CVE-2021-43515Improper Neutralization of Formula Elements in a CSV File in Kimai 2high7.8<1.14.11.14.1
CVE-2019-15481Kimai v2 is vulnerable to Cross-Site Scripting (XSS)medium6.1<1.11.1
CVE-2021-3983Cross-site Scripting in kimai2medium6.3<1.16.31.16.3
CVE-2021-4033Cross-Site Request Forgery in kimai2medium6.5<1.16.71.16.7
CVE-2021-3976Cross-site Scripting in kimai2medium4.3<1.16.21.16.2
CVE-2021-3963Cross-site Scripting in kimai2medium4.3<1.161.16
CVE-2021-3957Cross-site Scripting in kimai2medium4.6<1.161.16

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.