[Snyk] Security upgrade django from 2.2.28 to 3.2.15

[adamlaska]

This PR was automatically created by Snyk using the credentials of a real user.

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

xml2rfc 3.15.1 requires markupsafe, which is not installed.
xml2rfc 3.15.1 requires pycountry, which is not installed.
xml2rfc 3.15.1 requires jinja2, which is not installed.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	776/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 9.1	SQL Injection SNYK-PYTHON-DJANGO-2940618	django: 2.2.28 -> 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: 2.2.28 -> 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:

🦉 SQL Injection

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.