Skip to content
fr Sign in
6.1 Medium

CVE-2026-15920 An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8

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 and versions

Product Affected versions Fixed in
Django 6.0 6.0 → < 6.0.8 6.0.8
Django 5.2 5.2 → < 5.2.17 5.2.17

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Django

The 62 CVEs of Django →
CVE-2026-114582 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 5.3 Medium CVE-2026-113733 An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10 2.2 Low CVE-2026-113593 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 3.1 Low CVE-2026-111362 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 5.3 Medium
Track this CVE