# CVE-2019-19616: Path traversal in n/a

> Attackers can download arbitrary files from the Xtivia Web Time and Expense interface by manipulating attachment retrieval parameters.

- **Severity:** Medium 4.3 (`CVSS:3.0/AC:L/AV:N/A:N/C:L/I:N/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7qfc-f7pw-crm3

## What is CVE-2019-19616?

CVE-2019-19616 is a medium-severity path traversal vulnerability in n/a, published on 6 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Insecure Direct Object Reference (IDOR) vulnerability in the Xtivia Web Time and Expense (WebTE) interface used for Microsoft Dynamics NAV before 2017 allows an attacker to download arbitrary files by specifying arbitrary values for the recId and filename parameters of the /Home/GetAttachment function.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2019-19616?

It affects 1 product.


Products: Xtivia Web Time and Expense.

## How do I fix CVE-2019-19616?

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

## Is CVE-2019-19616 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19616 and fix it if it is affected.

What it is: CVE-2019-19616 is a medium-severity path traversal vulnerability in n/a, published on 6 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19616 in the wild and no public exploit code.

Affected product: n/a. 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-2019-19616/ (Markdown: https://insights.sbomify.com/CVE-2019-19616/index.md)
```

## Sources

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

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