CVE-2021-4033 json
Cross-Site Request Forgery (CSRF) in kevinpapst/kimai2
published 4y ago modified 4mo ago also GHSA-4jwx-78vx-gm6g , EUVD-2021-2440
- cvss
- 6.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
kimai2 is vulnerable to Cross-Site Request Forgery (CSRF)
Patch / fix
- packagist kevinpapst/kimai2 1.16.7
- kevinpapst kevinpapst/kimai2 1.16.7
Is CVE-2021-4033 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/e05be1f7-d00c-4cfd-9390-ccd9d1c737b7 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | kevinpapst/kimai2 | <1.16.7 |
1.16.7 |
Affected products
- kevinpapst kevinpapst/kimai2
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/kevinpapst/kimai2/commit/1da26e041df62c10bd8075d78f2db7854d3eee07
web, patch, third-party-advisory
-
huntr.dev
/bounties/e05be1f7-d00c-4cfd-9390-ccd9d1c737b7
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-4033
advisory
-
github.com
/kevinpapst/kimai2
package
Sources
- CVE List CVE-2021-4033
- GitHub Advisory GHSA-4jwx-78vx-gm6g
- NVD CVE-2021-4033
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.