CVE-2019-25317

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:vulncheck, epss
Elevated
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Kimai 2 contains a persistent cross-site scripting vulnerability that allows attackers to inject malicious scripts into timesheet descriptions. Attackers can insert SVG-based XSS payloads in the description field to execute arbitrary JavaScript when the page is loaded and viewed by other users.

CVSS v3
6.4
EG Score
6.4(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity64% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

February 11, 2026

Last Modified

June 23, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr.
github_pr Patch Available

fix possible xss in timesheet description

Patch available: kevinpapst/kimai2 2.35.1 (PR #962 merged 2019-07-14)

https://github.com/kevinpapst/kimai2/pull/962
generic

GitHub - kimai/kimai: Kimai is the #1 open-source time-tracking application. From freelancers to companies and organisations - everyone can manage timesheets, generate reports, create invoices and so much more... Web-based multi-user application, available as On-Premise or SaaS version: https://www.kimai.org · GitHub

https://github.com/kevinpapst/kimai2
generic🟡 PoC Available

Kimai 2 - Persistent Cross-Site Scripting - PHP webapps Exploit

https://www.exploit-db.com/exploits/47286

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
kimai/kimai0.1 ... 1.0.1 (13 versions)1.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 137 total refreshes for this CVE.

  1. 2026-09-22 14:43 UTCEPSS rescore
  2. 2026-09-21 20:28 UTCEPSS rescore
  3. 2026-09-20 20:10 UTCEPSS rescore
  4. 2026-09-18 22:06 UTCOSV refresh
  5. 2026-09-18 19:22 UTCEPSS rescore
  6. 2026-09-17 19:22 UTCEPSS rescore
  7. 2026-09-16 14:04 UTCEPSS rescore
  8. 2026-09-15 03:05 UTCEPSS rescore
  9. 2026-09-13 16:42 UTCEPSS rescore
  10. 2026-09-12 14:56 UTCEPSS rescore
  11. 2026-09-11 14:48 UTCEPSS rescore
  12. 2026-09-11 09:32 UTCEPSS rescore
  13. 2026-09-07 15:57 UTCEPSS rescore
  14. 2026-09-06 13:44 UTCEPSS rescore
  15. 2026-09-05 15:24 UTCEPSS rescore
  16. 2026-09-04 13:56 UTCEPSS rescore
  17. 2026-09-02 14:07 UTCEPSS rescore
  18. 2026-09-01 03:32 UTCEPSS rescore
  19. 2026-08-31 01:16 UTCOSV refresh
  20. 2026-08-30 19:13 UTCEPSS rescore
  21. 2026-08-30 01:18 UTCEPSS rescore
  22. 2026-08-28 21:36 UTCEPSS rescore
  23. 2026-08-26 14:42 UTCEPSS rescore
  24. 2026-08-25 13:45 UTCEPSS rescore
  25. 2026-08-24 14:11 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:45 UTCEPSS rescore
  2. 2026-08-20 22:51 UTCEPSS rescore
  3. 2026-08-19 17:00 UTCEPSS rescore
  4. 2026-08-18 13:44 UTCEPSS rescore
  5. 2026-08-17 13:43 UTCEPSS rescore
  6. 2026-08-16 14:52 UTCEPSS rescore
  7. 2026-08-16 02:10 UTCEPSS rescore
  8. 2026-08-15 01:26 UTCEPSS rescore
  9. 2026-08-14 10:24 UTCEG score recompute
  10. 2026-08-13 02:39 UTCEG score recompute
  11. 2026-08-12 13:47 UTCEPSS rescore
  12. 2026-08-11 09:16 UTCEG score recompute
  13. 2026-08-09 15:04 UTCEG score recompute
  14. 2026-08-09 13:43 UTCEPSS rescore
  15. 2026-08-08 16:33 UTCEPSS rescore
  16. 2026-08-07 22:13 UTCEG score recompute
  17. 2026-08-07 16:23 UTCEPSS rescore
  18. 2026-08-06 13:43 UTCEPSS rescore
  19. 2026-08-06 04:01 UTCEG score recompute
  20. 2026-08-05 19:13 UTCEPSS rescore
  21. 2026-08-04 15:05 UTCEPSS rescore
  22. 2026-08-02 20:51 UTCEG score recompute
  23. 2026-08-01 04:12 UTCEPSS rescore
  24. 2026-07-30 16:24 UTCEPSS rescore
  25. 2026-07-30 01:27 UTCEPSS rescore
  26. 2026-07-28 15:32 UTCEPSS rescore
  27. 2026-07-26 14:51 UTCEPSS rescore
  28. 2026-07-25 14:14 UTCEPSS rescore
  29. 2026-07-24 14:14 UTCEPSS rescore
  30. 2026-07-24 14:14 UTCEPSS rescore
  31. 2026-07-23 14:15 UTCEPSS rescore
  32. 2026-07-23 01:44 UTCEG score recompute
  33. 2026-07-22 22:24 UTCEG score recompute
  34. 2026-07-22 14:05 UTCEPSS rescore
  35. 2026-07-21 15:22 UTCEPSS rescore
  36. 2026-07-21 15:22 UTCEPSS rescore
  37. 2026-07-20 17:04 UTCEPSS rescore
  38. 2026-07-20 17:04 UTCEPSS rescore
  39. 2026-07-19 14:28 UTCEPSS rescore
  40. 2026-07-19 14:28 UTCEPSS rescore
  41. 2026-07-19 02:26 UTCEPSS rescore
  42. 2026-07-19 02:26 UTCEPSS rescore
  43. 2026-07-18 10:01 UTCEPSS rescore
  44. 2026-07-17 15:59 UTCOSV refresh
  45. 2026-07-16 16:59 UTCEPSS rescore
  46. 2026-07-16 16:59 UTCEPSS rescore
  47. 2026-07-15 16:55 UTCEPSS rescore
  48. 2026-07-15 16:55 UTCEPSS rescore
  49. 2026-07-13 22:27 UTCEPSS rescore
  50. 2026-07-13 06:10 UTCEPSS rescore
  51. 2026-07-13 06:10 UTCEPSS rescore
  52. 2026-07-12 05:43 UTCEPSS rescore
  53. 2026-07-12 05:43 UTCEPSS rescore
  54. 2026-07-11 08:24 UTCEPSS rescore
  55. 2026-07-11 08:24 UTCEPSS rescore
  56. 2026-07-09 19:06 UTCEPSS rescore
  57. 2026-07-08 15:11 UTCEPSS rescore
  58. 2026-07-07 13:43 UTCEPSS rescore
  59. 2026-07-06 16:25 UTCEPSS rescore
  60. 2026-07-06 16:25 UTCEPSS rescore
  61. 2026-07-06 02:20 UTCEPSS rescore
  62. 2026-07-05 02:27 UTCEPSS rescore
  63. 2026-07-04 06:28 UTCEPSS rescore
  64. 2026-07-01 15:03 UTCEPSS rescore
  65. 2026-07-01 15:03 UTCEPSS rescore
  66. 2026-06-30 23:20 UTCEPSS rescore
  67. 2026-06-29 14:23 UTCOSV refresh
  68. 2026-06-29 14:03 UTCEPSS rescore
  69. 2026-06-28 14:04 UTCEPSS rescore
  70. 2026-06-28 04:54 UTCEPSS rescore
  71. 2026-06-28 04:54 UTCEPSS rescore
  72. 2026-06-27 03:06 UTCEPSS rescore
  73. 2026-06-25 13:47 UTCEPSS rescore
  74. 2026-06-25 13:47 UTCEPSS rescore
  75. 2026-06-24 14:03 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-25317?
CVE-2019-25317 is a medium vulnerability published on February 11, 2026. Kimai 2 contains a persistent cross-site scripting vulnerability that allows attackers to inject malicious scripts into timesheet descriptions. Attackers can insert SVG-based XSS payloads in the description field to execute arbitrary JavaScript when the page is loaded and viewed by other users.
When was CVE-2019-25317 disclosed?
CVE-2019-25317 was first published in the National Vulnerability Database on February 11, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25317 actively exploited?
CVE-2019-25317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.2% of all scored CVEs.
What is the CVSS score of CVE-2019-25317?
CVE-2019-25317 has a CVSS v4.0 base score of 6.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2019-25317?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25317, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-25317

Explore →

Is Your Infrastructure Affected by CVE-2019-25317?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs