Arbitrary File Deletion vulnerability in OctoberCMSGHSA-jv6v-fvvx-4932
MEDIUMFix: octobercms/october@2b8939cGHSA-jv6v-fvvx-4932 is a medium-severity (CVSS 6.2) CWE-73 vulnerability in october/cms. 2 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.
EPSS Exploitation Probability
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
october/cmsReal-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 delete arbitrary 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:
<img width="1241" alt="Screen Shot 2020-03-31 at 12 16 53 PM" src="https://user-images.githubusercontent.com/7253840/78060872-89354d00-7349-11ea-8c2b-5881b0a50736.png">Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | october/cms | ≥ 1.0.319&&< 1.0.466 | 1.0.466composer require october/cms:^1.0.466 |
Affected Products
octoberoctobercmsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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 GHSA-jv6v-fvvx-4932 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
Is GHSA-jv6v-fvvx-4932 in your dependencies?
Find it across Packagist, including transitive dependencies.