2 results (0.001 seconds)

CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0

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. • https://github.com/statamic/cms/commit/0c07c10009a2439c8ee56c8faefd1319dc6e388d https://github.com/statamic/cms/commit/400875b20f40e1343699d536a432a6fc284346da https://github.com/statamic/cms/commit/4cc2c9bd0f39a93b3fc7e9ef0f12792576fd380d https://github.com/statamic/cms/security/advisories/GHSA-p7f6-8mcm-fwv3 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •

CVSS: 1.8EPSS: 0%CPEs: 1EXPL: 0

Statamic is a, Laravel + Git powered CMS designed for building websites. In affected versions users registering via the `user:register_form` tag will have their password confirmation stored in plain text in their user file. This only affects sites matching **all** of the following conditions: 1. Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week), 2. • https://dev.to/balogh08/cleaning-your-git-history-safely-removing-sensitive-data-10i5 https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository https://github.com/statamic/cms/commit/0b804306c96c99b81755d5bd02df87ddf392853e https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9 • CWE-312: Cleartext Storage of Sensitive Information •