6.1
MEDIUM CVSS 3.1
CVE-2026-15920
Potential cross-site scripting via URLField values in the admin
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.

INFO

Published Date :

Aug. 4, 2026, 5:16 p.m.

Last Modified :

Aug. 4, 2026, 6:16 p.m.

Remotely Exploit :

Yes !

Source :

6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
Affected Products

The following products are affected by CVE-2026-15920 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Djangoproject django
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 134c704f-9b21-4f2e-91b3-4a467353bcc0
CVSS 3.1 MEDIUM 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
CVSS 3.1 MEDIUM MITRE-CVE
CVSS 4.0 MEDIUM 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92
Solution
Update Django to a patched version to fix unsafe URL rendering in the admin.
  • Update Django to version 5.2.17 or later.
  • Update Django to version 6.0.8 or later.
  • Ensure model validation is used for URLField data.
  • Sanitize user-provided input before saving to the database.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-15920 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-15920 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-15920 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-15920 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Aug. 04, 2026

    Action Type Old Value New Value
    Added SSVC {'id': 'CVE-2026-15920', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-08-04T17:16:24.319084Z'}
  • New CVE Received by 6a34fbeb-21d4-45e7-8e0a-62b95bc12c92

    Aug. 04, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://github.com/django/django/', 'vendor': 'djangoproject', 'product': 'Django', 'versions': [{'status': 'affected', 'version': '6.0', 'lessThan': '6.0.8', 'versionType': 'python'}, {'status': 'unaffected', 'version': '6.0.8', 'versionType': 'python'}, {'status': 'affected', 'version': '5.2', 'lessThan': '5.2.17', 'versionType': 'python'}, {'status': 'unaffected', 'version': '5.2.17', 'versionType': 'python'}], 'packageName': 'django', 'collectionURL': 'https://pypi.org/project/Django/', 'defaultStatus': 'unaffected'}]
    Added 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.
    Added CVSS V4.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
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
    Added CWE CWE-83
    Added Reference https://docs.djangoproject.com/en/dev/releases/security/
    Added Reference https://github.com/django/django/commit/13debb622a32720bda1bccda7622fd14fbf3931b
    Added Reference https://github.com/django/django/commit/47511a21026cdd721d8fbf8571cc079bc38bb46d
    Added Reference https://github.com/django/django/commit/5a260d309a4c8010c2ebda24eb758a5d95e2508a
    Added Reference https://github.com/django/django/commit/b9adb81339cc418f8f56b1050cca6dfec3ab6349
    Added Reference https://groups.google.com/g/django-announce
    Added Reference https://www.djangoproject.com/weblog/2026/aug/04/security-releases/
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.