# CVE-2021-41139: Reflected XSS vulnerability in time.php

> Reflected XSS in Anuko Time Tracker allows attackers to execute malicious JavaScript in a logged-in user's browser via a crafted link.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2021
- **Updated:** 4 Aug 2024

## What is CVE-2021-41139?

CVE-2021-41139 is a high-severity cross-site scripting vulnerability in anuko timetracker, published on 13 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Anuko Time Tracker is an open source, web-based time tracking application written in PHP. When a logged on user selects a date in Time Tracker, it is being passed on via the date parameter in URI. Because of not checking this parameter for sanity in versions prior to 1.19.30.5600, it was possible to craft the URI with malicious JavaScript, use social engineering to convince logged on user to click on such link, and have the attacker-supplied JavaScript to be executed in user's browser. This issue is patched in version 1.19.30.5600. As a workaround, one may introduce `ttValidDbDateFormatDate` function as in the latest version and add a call to it within the access checks block in time.php.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2021-41139?

It affects 1 product.


Products: Anuko Time Tracker.

## How do I fix CVE-2021-41139?

No fix has been published for CVE-2021-41139 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41139 being exploited?

There is no known exploitation of CVE-2021-41139 in the wild and no public exploit code.

## Other vulnerabilities in anuko timetracker

- [CVE-2020-27422](https://insights.sbomify.com/CVE-2020-27422/): Business logic in n/a (critical 9.8)
- [CVE-2023-32306](https://insights.sbomify.com/CVE-2023-32306/): Time Tracker has Blind SQL Injection Vulnerability in Reports (high 8.8)
- [CVE-2020-15255](https://insights.sbomify.com/CVE-2020-15255/): CSV injection in Anuko Time Tracker (high 8.7)
- [CVE-2023-32308](https://insights.sbomify.com/CVE-2023-32308/): SQL Injection Vulnerability in anuko timetracker (high 8.2)
- [CVE-2021-43851](https://insights.sbomify.com/CVE-2021-43851/): SQL injection vulnerability in anuko timetracker (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41139 and fix it if it is affected.

What it is: CVE-2021-41139 is a high-severity cross-site scripting vulnerability in anuko timetracker, published on 13 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-41139 in the wild and no public exploit code.

Affected product: anuko timetracker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-41139/ (Markdown: https://insights.sbomify.com/CVE-2021-41139/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-41139
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-41139
- OSV: https://osv.dev/vulnerability/CVE-2021-41139

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-41139/
Summaries are generated and may contain mistakes; the official description above is the record.