[Snyk] Fix for 3 vulnerabilities

[robertatakenaka]

Snyk has created this PR to fix 3 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements/base.txt

⚠️ Warning

flower 2.0.1 requires tornado, which is not installed.
django-rosetta 0.10.1 has requirement Django>=4.2, but you have Django 3.2.25.
django-prometheus 2.4.1 has requirement Django<6.0,>=4.2, but you have Django 3.2.25.
celery 5.3.0 requires kombu, which is not installed.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• 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.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 SQL Injection
🦉 Allocation of Resources Without Limits or Throttling

[Copilot]

Pull request overview

This PR attempts to address security vulnerabilities identified by Snyk, but only partially implements the described fixes. The PR metadata claims to fix 3 vulnerabilities by upgrading Django (3.2.25 → 4.2.27) and sqlparse (0.4.4 → 0.5.4), but the actual changes only add a sqlparse version pin. The Django upgrade mentioned in the metadata is not reflected in the diff, and the current file already contains Django 5.2.7 (not 3.2.25 as stated in the PR description), suggesting a mismatch between the Snyk analysis and the actual codebase state.

Key changes:

• Adds sqlparse>=0.5.4 to address a SQL injection vulnerability
• No Django version changes are present in the diff despite being mentioned in the PR metadata

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The sqlparse security pin should be placed in the "SECURITY UPDATES" section (after line 138) along with other Snyk pins like certifi and requests, rather than at the end of the file after unrelated sections. This maintains better organization and makes security-related dependencies easier to locate and manage.

[Copilot]

Missing space after '#' in the comment. Should be # not directly required (with a space) to match the formatting style used in lines 137-138 for other Snyk security pins.

Suggested change

	sqlparse>=0.5.4 # not directly required, pinned by Snyk to avoid a vulnerability
	sqlparse>=0.5.4 # not directly required, pinned by Snyk to avoid a vulnerability