# CVE-2020-18647: Information disclosure in n/a

> Remote attackers can obtain sensitive information from NoneCMS via the vendor directory, exposing internal 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:** 22 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w5g2-9x75-q8j4

## What is CVE-2020-18647?

CVE-2020-18647 is a high-severity vulnerability in n/a, published on 22 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Information Disclosure in NoneCMS v1.3 allows remote attackers to obtain sensitive information via the component "/nonecms/vendor".

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: 5none Nonecms.

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

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

## Is CVE-2020-18647 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20062](https://insights.sbomify.com/CVE-2018-20062/): ThinkPHP "noneCms" Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2018-7219](https://insights.sbomify.com/CVE-2018-7219/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-18646](https://insights.sbomify.com/CVE-2020-18646/): Information disclosure in n/a (high 7.5)
- [CVE-2018-6029](https://insights.sbomify.com/CVE-2018-6029/): Server-side request forgery in n/a (high 7.5)
- [CVE-2019-16721](https://insights.sbomify.com/CVE-2019-16721/): Cross-site request forgery in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-18647 is a high-severity vulnerability in n/a, published on 22 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-18647 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-18647/ (Markdown: https://insights.sbomify.com/CVE-2020-18647/index.md)
```

## Sources

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

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