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.
- CVSS:
- 5.1 (nvd)
- Vector:
- 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:
- 0.35% (percentile 29.8)
- CWE:
- CWE-83
- Published:
- Modified:
- First seen:
- NVD status:
- Analyzed
- Aliases:
- CVE-2026-108147, CVE-2026-113593, CVE-2026-15337, CVE-2026-25674, CVE-2026-33033, CVE-2026-33034, CVE-2026-3902, CVE-2026-4277, CVE-2026-4292, CVE-2026-77050, CVE-2026-84429