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

> Attackers can exploit directory traversal and local file inclusion in Observium to achieve remote code execution via crafted URIs.

- **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:** 25 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-985f-4rhp-8wqw

## What is CVE-2020-25134?

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

### Official description

An issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to directory traversal and local file inclusion due to the fact that there is an unrestricted possibility of loading any file with an inc.php extension. Inclusion of other files (even though limited to the mentioned extension) can lead to Remote Code Execution. This can occur via /settings/?format=../ URIs to pages/settings.inc.php.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Observium Observium.

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

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

## Is CVE-2020-25134 being exploited?

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

Public exploit code:

- CVE-2020-25134 Authenticated Local File Inclusion in settings/format (github_poc): https://github.com/ynsmroztas/CVE-2020-25134

## Other vulnerabilities in n/a

- [CVE-2020-25132](https://insights.sbomify.com/CVE-2020-25132/): SQL injection in n/a (critical 9.8)
- [CVE-2020-25147](https://insights.sbomify.com/CVE-2020-25147/): SQL injection in n/a (critical 9.8)
- [CVE-2020-25133](https://insights.sbomify.com/CVE-2020-25133/): Path traversal in n/a (high 8.8)
- [CVE-2020-25136](https://insights.sbomify.com/CVE-2020-25136/): Path traversal in n/a (high 8.8)
- [CVE-2020-25143](https://insights.sbomify.com/CVE-2020-25143/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25134 is a high-severity path traversal vulnerability in n/a, published on 25 Sep 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-25134 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-25134/ (Markdown: https://insights.sbomify.com/CVE-2020-25134/index.md)
```

## Sources

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

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