[Snyk] Security upgrade django from 3.1.13 to 3.2.15

[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-dev.txt

⚠️ Warning

pylint-plugin-utils 0.6 requires pylint, which is not installed.
pylint-django 2.4.2 requires pylint, which is not installed.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	479/1000 Why? Has a fix available, CVSS 5.3	Access Restriction Bypass SNYK-PYTHON-DJANGO-2312875	django: 3.1.13 -> 3.2.15	No	No Known Exploit
	399/1000 Why? Has a fix available, CVSS 3.7	Directory Traversal SNYK-PYTHON-DJANGO-2329158	django: 3.1.13 -> 3.2.15	No	No Known Exploit
	399/1000 Why? Has a fix available, CVSS 3.7	Information Exposure SNYK-PYTHON-DJANGO-2329159	django: 3.1.13 -> 3.2.15	No	No Known Exploit
	479/1000 Why? Has a fix available, CVSS 5.3	Denial of Service (DoS) SNYK-PYTHON-DJANGO-2329160	django: 3.1.13 -> 3.2.15	No	No Known Exploit
	424/1000 Why? Has a fix available, CVSS 4.2	Cross-site Scripting (XSS) SNYK-PYTHON-DJANGO-2389002	django: 3.1.13 -> 3.2.15	No	No Known Exploit
	589/1000 Why? Has a fix available, CVSS 7.5	Denial of Service (DoS) SNYK-PYTHON-DJANGO-2389021	django: 3.1.13 -> 3.2.15	No	No Known Exploit
	704/1000 Why? Has a fix available, CVSS 9.8	SQL Injection SNYK-PYTHON-DJANGO-2606966	django: 3.1.13 -> 3.2.15	No	No Known Exploit
	811/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.8	SQL Injection SNYK-PYTHON-DJANGO-2606969	django: 3.1.13 -> 3.2.15	No	Proof of Concept
	776/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.1	SQL Injection SNYK-PYTHON-DJANGO-2940618	django: 3.1.13 -> 3.2.15	No	Proof of Concept
	564/1000 Why? Has a fix available, CVSS 7	Reflected File Download (RFD) SNYK-PYTHON-DJANGO-2968205	django: 3.1.13 -> 3.2.15	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 affected 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

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Access Restriction Bypass
🦉 Directory Traversal
🦉 Denial of Service (DoS)
🦉 More lessons are available in Snyk Learn