# CVE-2022-24708: Stored XSS vulnerability in anuko/timetracker

> A stored XSS vulnerability in Anuko Time Tracker allows logged-in users to inject JavaScript via group names, potentially executing code in other users' browsers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Feb 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-rgcm-xgvj-5mqh

## What is CVE-2022-24708?

CVE-2022-24708 is a medium-severity cross-site scripting vulnerability in anuko timetracker, published on 23 Feb 2022. Any signed-in user can exploit it over the network, 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. ttUser.class.php in Time Tracker versions prior to 1.20.0.5646 was not escaping primary group name for display. Because of that, it was possible for a logged in user to modify primary group name with elements of JavaScript. Such script could then be executed in user browser on subsequent requests on pages where primary group name was displayed. This is vulnerability has been fixed in version 1.20.0.5646. Users who are unable to upgrade may modify ttUser.class.php to use an additional call to htmlspecialchars when printing group name.

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

## Which versions are affected by CVE-2022-24708?

It affects 1 product.


Products: Anuko Time Tracker.

## How do I fix CVE-2022-24708?

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

## Is CVE-2022-24708 being exploited?

There is no known exploitation of CVE-2022-24708 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-2022-24708 and fix it if it is affected.

What it is: CVE-2022-24708 is a medium-severity cross-site scripting vulnerability in anuko timetracker, published on 23 Feb 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-24708 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-2022-24708/ (Markdown: https://insights.sbomify.com/CVE-2022-24708/index.md)
```

## Sources

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

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