[Snyk] Fix for 9 vulnerabilities

[snyk-bot]

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.txt

⚠️ Warning

``` social-auth-core 4.0.3 requires PyJWT, which is not installed. jsonfield 3.0.0 has requirement Django>=2.2, but you have Django 1.11.29. ```

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	369/1000 Why? Has a fix available, CVSS 3.1	Directory Traversal SNYK-PYTHON-DJANGO-1066259	django: 3.0.7 -> 3.1.10	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Web Cache Poisoning SNYK-PYTHON-DJANGO-1076802	django: 3.0.7 -> 3.1.10	No	No Known Exploit
	399/1000 Why? Has a fix available, CVSS 3.7	Directory Traversal SNYK-PYTHON-DJANGO-1090612	django: 3.0.7 -> 3.1.10	No	No Known Exploit
	379/1000 Why? Has a fix available, CVSS 3.3	Directory Traversal SNYK-PYTHON-DJANGO-1279042	django: 3.0.7 -> 3.1.10	No	No Known Exploit
	579/1000 Why? Has a fix available, CVSS 7.3	HTTP Header Injection SNYK-PYTHON-DJANGO-1290072	django: 3.0.7 -> 3.1.10	No	No Known Exploit
	579/1000 Why? Has a fix available, CVSS 7.3	Insecure Permissions SNYK-PYTHON-DJANGO-609368	django: 3.0.7 -> 3.1.10	No	No Known Exploit
	634/1000 Why? Has a fix available, CVSS 8.4	Insecure Permissions SNYK-PYTHON-DJANGO-609369	django: 3.0.7 -> 3.1.10	No	No Known Exploit
	539/1000 Why? Has a fix available, CVSS 6.5	Denial of Service (DoS) SNYK-PYTHON-DJANGOFILTER-1013846	django-filter: 2.2.0 -> 2.4.0	No	No Known Exploit
	529/1000 Why? Has a fix available, CVSS 6.3	Cross-site Scripting (XSS) SNYK-PYTHON-DJANGORESTFRAMEWORK-1090569	djangorestframework: 3.11.0 -> 3.11.2	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information: 🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic