# CVE-2019-20484: Missing authorization in n/a

> An attacker can read or modify project files by accessing URLs directly, bypassing project access controls.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2866-fxpg-497j

## What is CVE-2019-20484?

CVE-2019-20484 is a high-severity missing authorization vulnerability in n/a, published on 5 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Viki Vera 4.9.1.26180. A user without access to a project could download or upload project files by opening the Project URL directly in the browser after logging in.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Vikisolutions Vera.

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

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

## Is CVE-2019-20484 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-15123](https://insights.sbomify.com/CVE-2019-15123/): File upload in n/a (high 7.2)
- [CVE-2019-20483](https://insights.sbomify.com/CVE-2019-20483/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-20484 is a high-severity missing authorization vulnerability in n/a, published on 5 Jan 2021. 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-20484 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-20484/ (Markdown: https://insights.sbomify.com/CVE-2019-20484/index.md)
```

## Sources

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

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