# CVE-2020-25540: ThinkAdmin directory traversal vulnerability

> An unauthorized attacker can read arbitrary files on the remote server via a directory traversal vulnerability in ThinkAdmin.

- **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:** 14 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2qm5-r82g-5hcx

## What is CVE-2020-25540?

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

### Official description

ThinkAdmin v6 is affected by a directory traversal vulnerability. An unauthorized attacker can read arbitrarily file on a remote server via GET request encode parameter.

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

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

2 open source packages ship an affected version, including zoujingli/thinkadmin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zoujingli/thinkadmin` | Packagist | All versions | None |
| `zoujingli/thinkadmin` | Packagist | All versions | None |

Products: Thinkadmin Thinkadmin.

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

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

## Is CVE-2020-25540 being exploited?

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

Public exploit code:

- ThinkAdmin CVE-2020-25540 poc (github_poc): https://github.com/Schira4396/CVE-2020-25540
- ThinkAdmin 6 -  Arbitrarily File Read (exploitdb)
- ThinkAdmin CVE-2020-25540 POC (github_poc): https://github.com/RajChowdhury240/ThinkAdmin-CVE-2020-25540
- https://github.com/lowkey0808/cve-2020-25540 (github_poc): https://github.com/lowkey0808/cve-2020-25540
- ThinkAdmin v5 v6 任意文件读取漏洞利用，可自定义字典爆破 (github_poc): https://github.com/simonlee-hello/CVE-2020-25540
- ThinkAdmin 6 - Local File Inclusion (nuclei): http/cves/2020/CVE-2020-25540.yaml

## Other vulnerabilities in n/a

- [CVE-2020-23653](https://insights.sbomify.com/CVE-2020-23653/): ThinkAdmin insecure unserialize vulnerability (critical 9.8)
- [CVE-2019-11018](https://insights.sbomify.com/CVE-2019-11018/): ThinkAdmin Administrator cookies still working after password change (critical 9.8)
- [CVE-2023-48965](https://insights.sbomify.com/CVE-2023-48965/): File upload in n/a (high 8.8)
- [CVE-2023-48966](https://insights.sbomify.com/CVE-2023-48966/): ThinkAdmin arbitrary file upload vulnerability (high 8.8)
- [CVE-2020-35296](https://insights.sbomify.com/CVE-2020-35296/): ThinkAdmin Admin Panel Access using Default Credentials (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25540 is a high-severity path traversal vulnerability in n/a, published on 14 Sep 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-25540 exists.

Affected packages and fixed versions:
- zoujingli/thinkadmin (Packagist): affected all versions; no fix listed
- zoujingli/thinkadmin (Packagist): affected all versions; no fix listed

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

## Sources

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

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