# CVE-2020-15255: CSV injection in Anuko Time Tracker

> An attacker can inject malicious formulas into CSV exports, potentially leading to code execution when the file is opened in spreadsheet software.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **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:** 16 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-prjf-9mgh-8fpv

## What is CVE-2020-15255?

CVE-2020-15255 is a high-severity vulnerability in anuko timetracker, published on 16 Oct 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In Anuko Time Tracker before verion 1.19.23.5325, due to not properly filtered user input a CSV export of a report could contain cells that are treated as formulas by spreadsheet software (for example, when a cell value starts with an equal sign). This is fixed in version 1.19.23.5325.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2020-15255?

It affects 1 product.


Products: Anuko Time Tracker.

## How do I fix CVE-2020-15255?

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

## Is CVE-2020-15255 being exploited?

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

Public exploit code:

- Anuko Time Tracker 1.19.23.5325 - CSV/Formula Injection (exploitdb)

## 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-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)
- [CVE-2021-41139](https://insights.sbomify.com/CVE-2021-41139/): Reflected XSS vulnerability in time.php (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15255 and fix it if it is affected.

What it is: CVE-2020-15255 is a high-severity vulnerability in anuko timetracker, published on 16 Oct 2020. 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-2020-15255 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-2020-15255/ (Markdown: https://insights.sbomify.com/CVE-2020-15255/index.md)
```

## Sources

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

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