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

> Unauthenticated attackers can read arbitrary files via Local File Inclusion in LionWiki, exposing sensitive server data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j9vp-hmqw-qv3c

## What is CVE-2020-27191?

CVE-2020-27191 is a high-severity path traversal vulnerability in n/a, published on 16 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LionWiki before 3.2.12 allows an unauthenticated user to read files as the web server user via crafted string in the index.php f1 variable, aka Local File Inclusion. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

It affects 1 product.


Products: Lionwiki Lionwiki.

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

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

## Is CVE-2020-27191 being exploited?

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

Public exploit code:

- LionWiki <3.2.12 - Local File Inclusion (nuclei): http/cves/2020/CVE-2020-27191.yaml

## Other vulnerabilities in n/a

- [CVE-2009-3534](https://insights.sbomify.com/CVE-2009-3534/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27191 is a high-severity path traversal vulnerability in n/a, published on 16 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-27191 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-27191/ (Markdown: https://insights.sbomify.com/CVE-2020-27191/index.md)
```

## Sources

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

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