# CVE-2020-5295: Local File read vulnerability in OctoberCMS

> Authenticated backend users with asset management permissions can read arbitrary local files on the OctoberCMS server.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r23f-c2j5-rx2f

## What is CVE-2020-5295?

CVE-2020-5295 is a medium-severity path traversal vulnerability in Octobercms October, published on 3 Jun 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

In OctoberCMS (october/october composer package) versions from 1.0.319 and before 1.0.466, an attacker can exploit this vulnerability to read local files of an October CMS server. The vulnerability is only exploitable by an authenticated backend user with the `cms.manage_assets` permission. Issue has been patched in Build 466 (v1.0.466).

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere), CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `october/cms` | Packagist | From 1.0.319 | 1.0.466 |
| `october/cms` | Packagist | From 1.0.319 | 1.0.466 |

Products: Octobercms October.

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

Upgrade october/cms to 1.0.466 or later.

## Is CVE-2020-5295 being exploited?

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

Public exploit code:

- October CMS Build 465 - Arbitrary File Read Exploit (Authenticated) (exploitdb)

## Other vulnerabilities in Octobercms October

- [CVE-2021-32648](https://insights.sbomify.com/CVE-2021-32648/): October CMS Improper Authentication (high 8.2, exploited in the wild)
- [CVE-2021-3311](https://insights.sbomify.com/CVE-2021-3311/): October CMS Session ID not invalidated after logout (critical 9.8)
- [CVE-2017-1000194](https://insights.sbomify.com/CVE-2017-1000194/): October CMS File Upload Vulnerability (critical 9.8)
- [CVE-2017-1000196](https://insights.sbomify.com/CVE-2017-1000196/): Code injection in n/a (critical 9.8)
- [CVE-2017-1000197](https://insights.sbomify.com/CVE-2017-1000197/): Path traversal in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5295 is a medium-severity path traversal vulnerability in Octobercms October, published on 3 Jun 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-5295 in the wild and no public exploit code.

Affected packages and fixed versions:
- october/cms (Packagist): affected from 1.0.319; fixed in 1.0.466
- october/cms (Packagist): affected from 1.0.319; fixed in 1.0.466

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

## Sources

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

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