DjangoCRM django-crm Redirect common/urls.py toggle_default_sorting next_url redirect

Summaryinfo

A vulnerability, which was classified as problematic, was found in DjangoCRM django-crm. This impacts the function toggle_default_sorting of the file common/urls.py of the component Redirect. Executing a manipulation of the argument next_url can lead to redirect. The identification of this vulnerability is CVE-2026-71240. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic was found in DjangoCRM django-crm (affected version not known). This vulnerability affects the function toggle_default_sorting of the file common/urls.py of the component Redirect. The manipulation of the argument next_url with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. As an impact it is known to affect integrity. CVE summarizes:

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. This enables unauthenticated phishing redirects and referrer-based token leakage via redirect chains.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-71240 since 08/05/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 08/05/2026). The MITRE ATT&CK project declares the attack technique as T1204.001.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• DjangoCRM

Name

• django-crm

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion