CSRF Vulnerability Fix

This release fixes a security issue that was introduced in version 2.7.0. In that release, we made customizations to the Django middleware in order to disable some elements that were unnecessary for requests coming to the GraphQL API. Unfortunately, we inadvertently disabled CSRF protection for all POST requests coming to static Django views in Storefront 1.0 and Dashboard 1.0. An attacker could therefore send a request without the valid CSRF token, and the server would accept it. In this release, to close this loophole, we’ve reverted to the original middleware configuration. We felt that the performance gain was minimal and it wasn’t a crucial feature for the system, so the original solution is acceptable.

The issue was introduced on 16 May, 2019. Affected versions: 2.7.0

All users of the affected version are encouraged to upgrade Saleor immediately.

These are the highlights of the release. For the full changelog, go to the Github release page.

Thank You

This month we need to give 5,000 thanks 🙏 to all contributors, stargazers, and supporters of Saleor! We’ve just hit that landmark number of GitHub stars.

It’s not all about the numbers, but it is nice to track how far Saleor has come with your constant support. Here’s a little GIF we made to celebrate the occasion.

Contributing

For those of you who are interested in contributing to the project, we prepared a bunch of issues labeled as help wanted. Don’t worry if you don’t fully understand the problem — our team will try to guide you and answer all your questions. Remember to check our channels on Gitter and Spectrum; they serve best if you have quick questions that don’t require opening an issue on GitHub.