Impact
This is a high-impact, low-complexity attack vector. Users running Craft installations before 4.4.15 are encouraged to update to at least that version to mitigate the issue.
Mitigations
- This has been fixed in Craft 4.4.15. You should ensure you’re running at least that version.
- Refresh your security key in case it has already been captured. You can do that by running the
php craft setup/security-key command and copying the updated CRAFT_SECURITY_KEY environment variable to all production environments.
- If you have any other private keys stored as environment variables (e.g., S3 or Stripe), refresh those as well.
- Out of an abundance of caution, you may want to force all your users to reset their passwords in case your database was compromised. You can do that by running
php craft resave/users --set passwordResetRequired --to "fn() => true".
References
c0a37e1#diff-47dd43d86f85161944dfcce2e41d31955c4184672d9bd9d82b948c6b01b86476
7359d18
a270b92
https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#4415---2023-07-03-critical
Impact
This is a high-impact, low-complexity attack vector. Users running Craft installations before 4.4.15 are encouraged to update to at least that version to mitigate the issue.
Mitigations
php craft setup/security-keycommand and copying the updatedCRAFT_SECURITY_KEYenvironment variable to all production environments.php craft resave/users --set passwordResetRequired --to "fn() => true".References
c0a37e1#diff-47dd43d86f85161944dfcce2e41d31955c4184672d9bd9d82b948c6b01b86476
7359d18
a270b92
https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#4415---2023-07-03-critical