← Back

CVE-2026-15920

nvd nist
Published: Aug 4, 2026Modified: Aug 17, 2026

JSON object

Loading...
5.1
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
Show more
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:XShow less
Source: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92 (Secondary)

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 (2)

1 product
Django
Configuration A
2 vulnerable
Vulnerable SoftwareAffected Versions
Djangoproject
From 5.2 to 5.2.17
From 6.0 to 6.0.8

References (7)

Source: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
PatchVendor Advisory
Source: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
Mailing List
Source: 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
Vendor Advisory

Timeline

No history available yet.