CVE Watchtower

CVE-2026-15920djangoproject Django

NVD

Vulnerability Summary

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.
Severity Level
MEDIUM(6.1)
Published Date
Aug 4, 2026
Last Modified
Aug 4, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.39%Probability
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
CVSS v4.0 Base Metrics — Score 5.1 (MEDIUM)
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
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredNone
User InteractionActive
Confidentiality (Vulnerable System)None
Integrity (Vulnerable System)None
Availability (Vulnerable System)None
Confidentiality (Subsequent System)Low
Integrity (Subsequent System)Low
Availability (Subsequent System)None
Show CVSS v3.x metrics (score 6.1)
CVSS v3.1 Base Metrics — Score 6.1 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • djangoproject Django >= 6.0 and < 6.0.8
  • djangoproject Django >= 5.2 and < 5.2.17
Patched Versions
  • djangoproject Django 6.0.8
  • djangoproject Django 5.2.17

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run djangoproject Django and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Aug 4, 2026Published
  • Aug 4, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new djangoproject Django CVEsYou are reading CVE-2026-15920. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 18, 2026 18:39 UTC