cve.bz

CVE-2021-3957 kimai kimai 2: Cross Site Reference Forgery

4.3 mediumExploit referenceEPSS 0.4%Fix available

Medium (4.3) in kimai kimai 2. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in kevinpapst/kimai2 1.16.

On this page
kimai2 is vulnerable to Cross-Site Request Forgery (CSRF)

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-3957 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-3957?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-3957?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-3957 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
kevinpapst/kimai2before 1.16.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2xwq-h7r9-6w27Packagistkevinpapst/kimai2<1.161.16

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON