CVE-2026-15920: Potential cross-site scripting via URLField values in the admin

Published Aug 4, 2026
·
Updated

An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. django.contrib.admin.utils.displayforfield() 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 Software

2 affected components
Django<5.2.17
Django<6.0.8

Event History

Aug 4, 2026
CVE Published
via MITRE·03:48 PM
Data Sourced
via MITRE·03:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeakness
Nov 13, 58561
Event
via NVD·01:50 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-15920?

The severity of CVE-2026-15920 is rated as medium with a score of 6.1.

2

What vulnerability does CVE-2026-15920 address?

CVE-2026-15920 addresses a potential cross-site scripting issue in Django that arises from unvalidated URLField values in the admin interface.

3

How do I fix CVE-2026-15920?

To fix CVE-2026-15920, update to Django version 5.2.17 or later, or 6.0.8 or later.

4

What kind of impact does CVE-2026-15920 have?

CVE-2026-15920 could allow an attacker to execute malicious scripts in a user's browser by rendering unsafe URLField values.

5

Which versions of Django are affected by CVE-2026-15920?

CVE-2026-15920 affects Django versions prior to 5.2.17 and 6.0 before 6.0.8.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203