# CVE-2018-20405: Information disclosure in n/a

> Authenticated administrators can trigger syntax errors to disclose full file paths, though the issue is disputed as requiring high-level access.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/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:** 23 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qggm-xmg7-pqpf

## What is CVE-2018-20405?

CVE-2018-20405 is a low-severity vulnerability in n/a, published on 23 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

BigTree 4.3 allows full path disclosure via authenticated admin/news/ input that triggers a syntax error. NOTE: This has been disputed with the following reasoning: "The issue reported requires full developer level access to the content management system where cross site scripting is not an issue -- you already have full control of the CMS including running arbitrary PHP.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2018-20405?

It affects 1 product.


Products: Bigtreecms Bigtree.

## How do I fix CVE-2018-20405?

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

## Is CVE-2018-20405 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20405 and fix it if it is affected.

What it is: CVE-2018-20405 is a low-severity vulnerability in n/a, published on 23 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-20405 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-2018-20405/ (Markdown: https://insights.sbomify.com/CVE-2018-20405/index.md)
```

## Sources

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

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