Statamic CMS has Path Traversal in Asset Upload
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.6%
exploitation probability
0.6%top 56% of all CVEs
observed exploitation
nono source reports it
Statmatic is a Laravel and Git powered content management system (CMS). Prior to version 5.17.0, assets uploaded with appropriately crafted filenames may result in them being placed in a location different than what was configured. The issue affects front-end forms with `assets` fields and other places where assets can be uploaded, although users would need upload permissions anyway. Files can be uploaded so they would be located on the server in a different location, and potentially override existing files. Traversal outside an asset container is not possible. This path traversal vulnerability has been fixed in 5.17.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Affected products
statamic · cmsReferences
https://github.com/statamic/cms/commit/0c07c10009a2439c8ee56c8faefd1319dc6e388dhttps://github.com/statamic/cms/commit/400875b20f40e1343699d536a432a6fc284346dahttps://github.com/statamic/cms/commit/4cc2c9bd0f39a93b3fc7e9ef0f12792576fd380dhttps://github.com/statamic/cms/security/advisories/GHSA-p7f6-8mcm-fwv3