PYSEC-2019-17: django fixed in 2.1.5, 2.0.10 and 1.11.18

PYSEC-2019-17 PUBLISHED

Record from OSV · Published January 9, 2019

django is fixed in 2.1.5, 2.0.10 and 1.11.18 (PyPI)

In Django 1.11.x before 1.11.18, 2.0.x before 2.0.10, and 2.1.x before 2.1.5, an Improper Neutralization of Special Elements in Output Used by a Downstream Component issue exists in django.views.defaults.page_not_found(), leading to content spoofing (in a 404 error page) if a user fails to recognize that a crafted URL has malicious content.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

Package	Ecosystem	Fixed in
django	PyPI	2.1.5, 2.0.10, 1.11.18

Affected products

Vendor	Product	Versions
PyPI	django	1.11, 2.0, 2.1

Timeline

Jan 9, 2019 CVE Published
Nov 8, 2023 CVE Updated
May 18, 2026 Distribution Patch
May 18, 2026 Security Advisory

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln PYSEC-2019-17
vulnetix vdb fixes PYSEC-2019-17

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/PYSEC-2019-17/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →