How severe is CVE-2020-5295?

CVE-2020-5295 has a CVSS score of 4.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-5295?

CVE-2020-5295 affects the following packages: october/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2020-5295?

Update october/cms to 1.0.466 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-5295 is resolved across your whole dependency graph.

How do I detect CVE-2020-5295 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-5295 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2020-5295 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2020-5295, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-5295?

CVE-2020-5295 has an EPSS (Exploit Prediction Scoring System) score of 7.4%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-5295?

CVE-2020-5295 is classified as CWE-98 (CWE-98), CWE-829 (CWE-829). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-5295 published, and has it been updated?

CVE-2020-5295 was published on June 3, 2020 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2020-5295 — cms

MEDIUMFix: octobercms/october@2b8939c

CVE-2020-5295 is a medium-severity (CVSS 4.9) CWE-98 vulnerability in october/cms. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for october/cms — see the affected versions and patch details below.

Local File read vulnerability in OctoberCMS

Also known asGHSA-r23f-c2j5-rx2f

Published

Jun 3, 2020

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

7.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘october/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.

Patches

Issue has been patched in Build 466 (v1.0.466).

Workarounds

Apply https://github.com/octobercms/october/commit/2b8939cc8b5b6fe81e093fe2c9f883ada4e3c8cc to your installation manually if unable to upgrade to Build 466.

References

Reported by Sivanesh Ashok

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Threat assessment:

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`october/cms`	≥ 1.0.319&&< 1.0.466	1.0.466`composer require october/cms:^1.0.466`

Affected Products

1 product · 1 configurations

Application

octoberoctobercms

≥ 1.0.319 && < 1.0.466

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-49045webappsphp

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

by Sivanesh Ashok · Nov 13, 2020

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update october/cms to 1.0.466 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-5295 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact 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. ### Patches Issue has been patched in Build 466 (v1.0.466). ### Workarounds Apply https://github.com/octobercms/october/commit/2b8939cc8b5b6fe81e093fe2c9f883ada4e3c8cc to your installation manually if unable to upgrade to Build 466. ### References Reported by [Sivanesh Ashok](https://stazot.com/) ### For more information If you have any questions or comments about this advisory: *