[Snyk] Security upgrade django from 1.11.29 to 3.2.15

[francesco-filicetti]

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

djangosaml2 1.5.3 requires pysaml2, which is not installed.
djangosaml2 1.5.3 has requirement Django<5,>=2.2, but you have Django 1.11.29.
design-django-theme 1.6.4 requires django-sass-processor, which is not installed.

Vulnerabilities that will be fixed

By pinning:

Severity	Issue	Upgrade	Breaking Change	Exploit Maturity
	Directory Traversal SNYK-PYTHON-DJANGO-1066259	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	Directory Traversal SNYK-PYTHON-DJANGO-1279042	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	HTTP Header Injection SNYK-PYTHON-DJANGO-1290072	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	Directory Traversal SNYK-PYTHON-DJANGO-1298665	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	Access Restriction Bypass SNYK-PYTHON-DJANGO-2312875	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	Directory Traversal SNYK-PYTHON-DJANGO-2329158	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	Information Exposure SNYK-PYTHON-DJANGO-2329159	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-DJANGO-2329160	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	Cross-site Scripting (XSS) SNYK-PYTHON-DJANGO-2389002	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	Denial of Service (DoS) SNYK-PYTHON-DJANGO-2389021	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	SQL Injection SNYK-PYTHON-DJANGO-2606966	django: 1.11.29 -> 3.2.15	No	No Known Exploit
	SQL Injection SNYK-PYTHON-DJANGO-2606969	django: 1.11.29 -> 3.2.15	No	Proof of Concept
	SQL Injection SNYK-PYTHON-DJANGO-2940618	django: 1.11.29 -> 3.2.15	No	Proof of Concept
	Reflected File Download (RFD) SNYK-PYTHON-DJANGO-2968205	django: 1.11.29 -> 3.2.15	No	No Known Exploit

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:

🦉 Directory Traversal
🦉 Directory Traversal
🦉 Directory Traversal
🦉 More lessons are available in Snyk Learn