How severe is CVE-2019-15481?

CVE-2019-15481 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-15481?

CVE-2019-15481 affects the following packages: kevinpapst/kimai2 (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-15481?

Update kevinpapst/kimai2 to 1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-15481 is resolved across your whole dependency graph.

How do I detect CVE-2019-15481 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kevinpapst/kimai2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-15481 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2019-15481 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-15481 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-15481?

CVE-2019-15481 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-15481?

CVE-2019-15481 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-15481 published, and has it been updated?

CVE-2019-15481 was published on August 23, 2019 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2019-15481 — kimai2

MEDIUMFix: kevinpapst/kimai2#962

CVE-2019-15481 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in kevinpapst/kimai2. A fix is available for kevinpapst/kimai2 — see the affected versions and patch details below.

Kimai v2 is vulnerable to Cross-Site Scripting (XSS)

Also known asGHSA-7v44-75jf-22gj

Published

Aug 23, 2019

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘kevinpapst/kimai2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Kimai v2 before 1.1 has XSS via a timesheet description.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`kevinpapst/kimai2`	all versions	1.1`composer require kevinpapst/kimai2:^1.1`

Affected Products

1 product · 1 configurations

Application

kimai 2kimai

< 1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kevinpapst/kimai2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kevinpapst/kimai2 to 1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-15481 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Kimai v2 before 1.1 has XSS via a timesheet description.

O3 Security · Impact-Aware SCA

Is CVE-2019-15481 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

kimai2

5.9/10

Code-Review1/10

Maintained10/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Aug 23, 2019

Last updated

Oct 20, 2026

Identifiers

CVE-2019-15481

GHSA-7v44-75jf-22gj

References

Advisorynvd.nist.gov · CVE 2019 15481 Fixgithub.com Reportgithub.com · 1.1 Packagegithub.com · kimai2

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting kevinpapst/kimai2 are rated as high or higher (top: high).

CVE-2021-43515CVE-2021-4033CVE-2021-3983CVE-2021-3992CVE-2021-3985CVE-2021-3957CVE-2021-3976CVE-2021-3963

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026