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

> Authenticated attackers can exploit directory traversal in Lotus Core CMS to include arbitrary PHP files, potentially leading to code execution or data disclosure.

- **Severity:** High 8.8 (`CVSS:3.1/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:** 5 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8pfr-qgrr-4cqf

## What is CVE-2020-8641?

CVE-2020-8641 is a high-severity path traversal vulnerability in n/a, published on 5 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Lotus Core CMS 1.0.1 allows authenticated Local File Inclusion of .php files via directory traversal in the index.php page_slug parameter.

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

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

It affects 1 product.


Products: Lotus Core Cms Project Lotus Core Cms.

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

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

## Is CVE-2020-8641 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-8641 exists.

Public exploit code:

- Lotus Core CMS 1.0.1 - Local File Inclusion (nuclei): http/cves/2020/CVE-2020-8641.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2020-8641 is a high-severity path traversal vulnerability in n/a, published on 5 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-8641 exists.

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-8641/ (Markdown: https://insights.sbomify.com/CVE-2020-8641/index.md)
```

## Sources

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

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