Description
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.contrib.admin.utils.display_for_field()` renders `URLField` values as clickable links in the admin without validating the URL. A value stored with an unsafe scheme is displayed as a link on changelist and read-only admin pages, which allows cross-site scripting against staff users who click the link. Exploitation requires the unsafe value to already be stored in the database. `URLField` validation through a `ModelForm` or the admin rejects unsafe schemes, so this affects applications that persist `URLField` data without running model validation, for example through direct queryset writes, deserialization, or bulk import of untrusted input. Django would like to thank Egor Saltykov for reporting this issue.
Affected products
djangoproject: django
References7
- docs.djangoproject.com/en/dev/releases/security/ PatchVendor Advisory
- www.djangoproject.com/weblog/2026/aug/04/security-releases/ Vendor Advisory
- github.com/django/django/commit/13debb622a32720bda1bccda7622fd1… Patch
- github.com/django/django/commit/47511a21026cdd721d8fbf8571cc079… Patch
- github.com/django/django/commit/5a260d309a4c8010c2ebda24eb758a5… Patch
- github.com/django/django/commit/b9adb81339cc418f8f56b1050cca6df… Patch
- groups.google.com/g/django-announce Mailing List
Metrics
- CVSS 3.1
-
6.1
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N - CVSS 4.0
-
5.1
MEDIUM
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 0% percentile: 30 · as of 13 November 2026
- CWE
- CWE-83
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.