# CVE-2026-71240: DjangoCRM - Unauthenticated Open Redirect via toggle_default_sorting next_url Parameter

> Unauthenticated attackers can redirect users to arbitrary same-site paths via the toggle_default_sorting view, bypassing intended navigation controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-q389-cg45-h4hc

## What is CVE-2026-71240?

CVE-2026-71240 is a medium-severity vulnerability in DjangoCRM django-crm, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

DjangoCRM's toggle_default_sorting view is the only route in common/urls.py that is not wrapped in login_required or staff_member_required, and it redirects to a caller-supplied next_url GET parameter after only checking secure_url(next_url), which merely verifies the target host matches the current site's domain (blocking only cross-domain redirects) while allowing any same-site path with no authentication required to reach the view.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-71240?


## How do I fix CVE-2026-71240?

No fix has been published for CVE-2026-71240 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71240 being exploited?

There is no known exploitation of CVE-2026-71240 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71240 and fix it if it is affected.

What it is: CVE-2026-71240 is a medium-severity vulnerability in DjangoCRM django-crm, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-71240 in the wild and no public exploit code.

Affected product: DjangoCRM django-crm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71240/ (Markdown: https://insights.sbomify.com/CVE-2026-71240/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71240
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71240
- OSV: https://osv.dev/vulnerability/CVE-2026-71240

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71240/
Summaries are generated and may contain mistakes; the official description above is the record.