🛡️ CVE-2013-1665 — django

⚪ Unknown ✅ No Known Exploit CWE-200 OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

XML External Entity (XXE) in Django

The XML libraries for Python as used in OpenStack Keystone Essex and Folsom, Django, and possibly other products allow remote attackers to read arbitrary files via an XML external entity declaration in conjunction with an entity reference, aka an XML External Entity (XXE) attack.

Weakness class

CVE-2013-1665 is classified as CWE-200: Exposure of Sensitive Information. Information that should stay internal is disclosed to someone who is not authorised to see it.

Affected software

CVE-2013-1665 is recorded against 1 package.

  • django (from 1.4.0 up to 1.4.4)

Timeline and source

Published on 17 May 2022 and last revised on 7 July 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
bugs.launchpad.net (Web)
blog.python.org (Web)
bugs.python.org (Web)
lists.openstack.org (Web)
rhn.redhat.com (Web)
rhn.redhat.com (Web)
rhn.redhat.com (Web)
ubuntu.com (Web)
www.debian.org (Web)
www.openwall.com (Web)
www.openwall.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE CWE-200
Public Exploit ✅ No
Source OSV
Published 2022-05-17
Updated 2026-08-12
Modified 2026-07-07
Fix URL N/A

Affected Packages

Software From version Fixed in
django 1.4.0 1.4.4

References

Free Vulnerability Check

Is your site affected by CVE-2013-1665?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2013-1665 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.