# CVE-2018-1000619: File upload in n/a

> Authenticated attackers with upload permissions can achieve remote code execution via unsanitized input in Ovidentia.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 9 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-59c9-ppc4-4v7h

## What is CVE-2018-1000619?

CVE-2018-1000619 is a high-severity vulnerability in n/a, published on 9 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ovidentia version 8.4.3 and earlier contains a Unsanitized User Input vulnerability in utilit.php, bab_getAddonFilePathfromTg that can result in Authenticated Remote Code Execution. This attack appear to be exploitable via The attacker must have permission to upload addons.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2018-1000619?

It affects 1 product.


Products: Ovidentia Ovidentia.

## How do I fix CVE-2018-1000619?

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

## Is CVE-2018-1000619 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13978](https://insights.sbomify.com/CVE-2019-13978/): SQL injection in n/a (high 8.8)
- [CVE-2022-22914](https://insights.sbomify.com/CVE-2022-22914/): Path traversal in n/a (high 7.5)
- [CVE-2008-3918](https://insights.sbomify.com/CVE-2008-3918/): SQL injection in n/a (high 7.5)
- [CVE-2008-4423](https://insights.sbomify.com/CVE-2008-4423/): SQL injection in n/a (medium 6.5)
- [CVE-2021-29343](https://insights.sbomify.com/CVE-2021-29343/): SQL injection in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000619 and fix it if it is affected.

What it is: CVE-2018-1000619 is a high-severity vulnerability in n/a, published on 9 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000619 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-2018-1000619/ (Markdown: https://insights.sbomify.com/CVE-2018-1000619/index.md)
```

## Sources

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

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