CVE-2026-71240: CWE-601 URL Redirection to Untrusted Site in DjangoCRM django-crm
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.
AI Analysis
Technical Summary
The vulnerability in DjangoCRM's django-crm product involves the toggle_default_sorting view, which is not protected by authentication decorators like login_required or staff_member_required. It redirects users based on a next_url GET parameter after checking only that the URL's host matches the current site domain, blocking cross-domain redirects but allowing any same-site path. Because no authentication is required to access this view, attackers can craft URLs that redirect users to malicious same-site paths, enabling phishing attacks and referrer-based token leakage through redirect chains. This is classified as CWE-601 (URL Redirection to Untrusted Site).
Potential Impact
An attacker can exploit this vulnerability to perform phishing attacks by redirecting users to malicious pages within the same domain without authentication. Additionally, sensitive tokens or information could be leaked via referrer headers in redirect chains. There is no direct impact on confidentiality or availability beyond these redirect-based risks.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the toggle_default_sorting view by applying appropriate authentication controls such as login_required or staff_member_required decorators. Validate and sanitize the next_url parameter more strictly to ensure it does not allow unsafe redirects even within the same domain.
CVE-2026-71240: CWE-601 URL Redirection to Untrusted Site in DjangoCRM django-crm
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. This enables unauthenticated phishing redirects and referrer-based token leakage via redirect chains.
CVSS v3.1
Score 4.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in DjangoCRM's django-crm product involves the toggle_default_sorting view, which is not protected by authentication decorators like login_required or staff_member_required. It redirects users based on a next_url GET parameter after checking only that the URL's host matches the current site domain, blocking cross-domain redirects but allowing any same-site path. Because no authentication is required to access this view, attackers can craft URLs that redirect users to malicious same-site paths, enabling phishing attacks and referrer-based token leakage through redirect chains. This is classified as CWE-601 (URL Redirection to Untrusted Site).
Potential Impact
An attacker can exploit this vulnerability to perform phishing attacks by redirecting users to malicious pages within the same domain without authentication. Additionally, sensitive tokens or information could be leaked via referrer headers in redirect chains. There is no direct impact on confidentiality or availability beyond these redirect-based risks.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the toggle_default_sorting view by applying appropriate authentication controls such as login_required or staff_member_required decorators. Validate and sanitize the next_url parameter more strictly to ensure it does not allow unsafe redirects even within the same domain.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- TuranSec
- Date Reserved
- 2026-08-05T10:53:53.175Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a731a81bf8831d539c95ca5
Added to database: 08/05/2026, 11:12:01 UTC
Last enriched: 08/05/2026, 11:27:06 UTC
Last updated: 08/06/2026, 03:03:27 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.