[Snyk] Security upgrade django from 2.2.24 to 3.2.25

[Abuchtela]

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/base.txt

⚠️ Warning

wiki 0.7.3 has requirement bleach<3.2,>=3.1.0, but you have bleach 6.0.0.
wiki 0.7.3 has requirement Django<3.2,>=2.1, but you have Django 3.2.25.
web3 4.5.0 has requirement websockets<6.0.0,>=5.0.1, but you have websockets 11.0.3.
web3 4.5.0 has requirement eth-account<0.4.0,>=0.2.1, but you have eth-account 0.5.9.
twilio 9.0.0 has requirement PyJWT<3.0.0,>=2.0.0, but you have PyJWT 1.5.3.
social-auth-core 4.4.2 has requirement PyJWT>=2.0.0, but you have PyJWT 1.5.3.
rlp 3.0.0 has requirement eth-utils<3,>=2.0.0, but you have eth-utils 1.4.1.
PyGithub 1.54 has requirement requests<2.25,>=2.14.0, but you have requests 2.31.0.
mkdocs 1.2.3 has requirement watchdog>=2.0, but you have watchdog 0.9.0.
eth-testrpc 1.3.5 has requirement rlp<=0.6.0,>=0.4.7, but you have rlp 3.0.0.
eth-tester 0.9.1b2 has requirement eth-utils<3.0.0,>=2.0.0, but you have eth-utils 1.4.1.
eth-tester 0.9.1b2 has requirement eth-abi>=3.0.1, but you have eth-abi 1.1.1.
eth-tester 0.9.1b2 has requirement eth-account>=0.6.0, but you have eth-account 0.5.9.
eth-rlp 0.3.0 has requirement eth-utils<3,>=2.0.0, but you have eth-utils 1.4.1.
eth-keys 0.4.0 has requirement eth-utils<3.0.0,>=2.0.0, but you have eth-utils 1.4.1.
eth-keys 0.4.0 has requirement eth-typing<4,>=3.0.0, but you have eth-typing 2.3.0.
eth-account 0.5.9 has requirement rlp<3,>=1.0.0, but you have rlp 3.0.0.
eth-account 0.5.9 has requirement eth-abi<3,>=2.0.0b7, but you have eth-abi 1.1.1.
eth-account 0.5.9 has requirement eth-keys<0.4.0,>=0.3.4, but you have eth-keys 0.4.0.
elasticsearch 7.10.0 has requirement urllib3<2,>=1.21.1, but you have urllib3 2.0.7.
django-sekizai 3.0.1 has requirement django-classy-tags>=1, but you have django-classy-tags 0.8.0.
django-admin-sortable2 0.7.6 has requirement Django<3.1,>=1.8, but you have Django 3.2.25.
ddtrace 2.7.0 has requirement importlib-metadata<=6.5.0; python_version < "3.8", but you have importlib-metadata 6.7.0.
ccxt 4.2.59 has requirement cryptography>=2.6.1, but you have cryptography 2.3.
botocore 1.21.65 has requirement urllib3<1.27,>=1.25.4, but you have urllib3 2.0.7.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	50/1000 Why? Confidentiality impact: None, Integrity impact: None, Availability impact: Low, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.01055, Social Trends: No, Days since published: 0, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 2.35, Likelihood: 2.08, Score Version: V5	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-DJANGO-6370660	django: 2.2.24 -> 3.2.25	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:

🦉 Regular Expression Denial of Service (ReDoS)