[Snyk] Security upgrade django from 3.2.25 to 4.2.28

[robertatakenaka]

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

Snyk changed the following file(s):

• requirements/local.txt

⚠️ Warning

django-extensions 3.2.3 requires Django, 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

[Copilot]

Pull request overview

This PR attempts to fix a security vulnerability (SNYK-PYTHON-DJANGO-15183335) by upgrading Django from version 3.2.25 to 4.2.28. However, the codebase currently specifies django==5.2.3 in requirements/base.txt, revealing significant issues with the project's Django version management.

Changes:

• Adds django>=4.2.28 to requirements/local.txt as a Snyk-pinned dependency
• Aims to address a SQL injection vulnerability

[Copilot]

This change introduces a version conflict with the Django version already specified in base.txt. The base.txt file (which is included via -r base.txt on line 1) specifies django==5.2.3 on line 30, but this change adds django>=4.2.28.

This creates conflicting requirements:

• base.txt requires exactly Django 5.2.3
• local.txt now requires Django >= 4.2.28

Since Django 5.2.3 satisfies the >=4.2.28 constraint, pip might resolve this to Django 5.2.3, making this line redundant. However, this approach is confusing and can lead to maintenance issues.

The correct approach would be to update the Django version in base.txt to address the security vulnerability, rather than adding a conflicting requirement in local.txt. The security fix should apply to all environments (local, production, etc.), not just the local development environment.

Suggested change

django>=4.2.28 # not directly required, pinned by Snyk to avoid a vulnerability

[Copilot]

The PR description mentions upgrading Django from 3.2.25 to 4.2.28, but the codebase actually has Django 5.2.3 specified in requirements/base.txt (line 30). This indicates a significant discrepancy between what the PR claims to do and the actual state of the codebase.

Either:

1. The PR description is based on outdated information about the project's Django version, or
2. There's confusion about which version is currently in use

The security vulnerability fix (SNYK-PYTHON-DJANGO-15183335) should be evaluated against Django 5.2.3, not 3.2.25, to determine if it's even necessary. Django 5.2.3 may already have the security fix that this PR is attempting to apply.