CVE-2026-15920
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 5.1 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-83
- Record status
- Analyzed
Affected
- Djangoproject Django < 5.2.17
- Djangoproject Django < 6.0.8
Attack profile CVSS 4.0 · 5.1
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- None
- Privileges needed
- None
- User interaction
- Active
- Confidentiality
- None
- Integrity
- None
- Availability
- None
Raw 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
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-15920.md and follow it. Check whether this project is affected by CVE-2026-15920. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://docs.djangoproject.com/en/dev/releases/security/
- https://github.com/django/django/commit/13debb622a32720bda1bccda7622fd14fbf3931b
- https://github.com/django/django/commit/47511a21026cdd721d8fbf8571cc079bc38bb46d
- https://github.com/django/django/commit/5a260d309a4c8010c2ebda24eb758a5d95e2508a
- https://github.com/django/django/commit/b9adb81339cc418f8f56b1050cca6dfec3ab6349
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases/
References
- https://docs.djangoproject.com/en/dev/releases/security/
- https://github.com/django/django/commit/13debb622a32720bda1bccda7622fd14fbf3931b
- https://github.com/django/django/commit/47511a21026cdd721d8fbf8571cc079bc38bb46d
- https://github.com/django/django/commit/5a260d309a4c8010c2ebda24eb758a5d95e2508a
- https://github.com/django/django/commit/b9adb81339cc418f8f56b1050cca6dfec3ab6349
- https://groups.google.com/g/django-announce
- https://www.djangoproject.com/weblog/2026/aug/04/security-releases/