# CVE-2021-46203: Path traversal in n/a

> Attackers can read arbitrary files from the server via a path traversal vulnerability in the path parameter of Taocms.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 19 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jh95-qvfh-rjjw

## What is CVE-2021-46203?

CVE-2021-46203 is a medium-severity path traversal vulnerability in n/a, published on 19 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Taocms v3.0.2 was discovered to contain an arbitrary file read vulnerability via the path parameter.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-46203?

It affects 1 product.


Products: Taogogo Taocms.

## How do I fix CVE-2021-46203?

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

## Is CVE-2021-46203 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-33350](https://insights.sbomify.com/CVE-2024-33350/): Path traversal in n/a (critical 9.8)
- [CVE-2022-48006](https://insights.sbomify.com/CVE-2022-48006/): File upload in n/a (critical 9.8)
- [CVE-2022-46998](https://insights.sbomify.com/CVE-2022-46998/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2022-36262](https://insights.sbomify.com/CVE-2022-36262/): Code injection in n/a (critical 9.8)
- [CVE-2022-23880](https://insights.sbomify.com/CVE-2022-23880/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46203 and fix it if it is affected.

What it is: CVE-2021-46203 is a medium-severity path traversal vulnerability in n/a, published on 19 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-46203 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-2021-46203/ (Markdown: https://insights.sbomify.com/CVE-2021-46203/index.md)
```

## Sources

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

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