Craft CMS
Craft CMS stores user-provided content in session files
Craft CMS stores arbitrary content provided by unauthenticated users in session files. This content could be accessed and executed, possibly using an independent vulnerability. Craft CMS redirects requests that require authentication to the login page and generates a session file on the server at '/var/lib/php/sessions'. Such session files are named 'sess_[session_value]', where '[session_value]' is provided to the client in a 'Set-Cookie' response header. Craft CMS stores the return URL requested by the client without sanitizing parameters. Consequently, an unauthenticated client can introduce arbitrary values, such as PHP code, to a known local file location on the server. Craft CMS versions 5.7.5 and 4.15.3 have been released to address this issue.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 5.7.5
- < 4.15.3
Fixed in 5.7.5, 4.15.3
Mitigation
Upgrade CMS to 5.7.5 or 4.15.3 or later.
References
- Patch github.com/craftcms/cms/pull/17220
- Release notes github.com/craftcms/cms/releases/tag/4.15.3
- Release notes github.com/craftcms/cms/releases/tag/5.7.5
Timeline
Days relative to CVE publicationNo public PoC found yet; added to CISA KEV 26 days after publication.
PoC repositories
Found on GitHub.No PoC repositories found yet.