# CVE-2020-21431: Path traversal in n/a

> Attackers can read and write arbitrary files via the template editor, potentially compromising the CMS integrity and data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hp63-x8c8-jq88

## What is CVE-2020-21431?

CVE-2020-21431 is a medium-severity path traversal vulnerability in n/a, published on 4 Oct 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

HongCMS v3.0 contains an arbitrary file read and write vulnerability in the component /admin/index.php/template/edit.

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

It affects 1 product.


Products: Hongcms Project Hongcms.

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

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

## Is CVE-2020-21431 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-18178](https://insights.sbomify.com/CVE-2020-18178/): Path traversal in n/a (critical 9.8)
- [CVE-2020-21252](https://insights.sbomify.com/CVE-2020-21252/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-10265](https://insights.sbomify.com/CVE-2018-10265/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-28523](https://insights.sbomify.com/CVE-2022-28523/): Path traversal in n/a (high 8.1)
- [CVE-2018-16774](https://insights.sbomify.com/CVE-2018-16774/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-21431 is a medium-severity path traversal vulnerability in n/a, published on 4 Oct 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-21431 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-2020-21431/ (Markdown: https://insights.sbomify.com/CVE-2020-21431/index.md)
```

## Sources

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

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