How severe is CVE-2013-1665?

No CVSS score has been assigned to CVE-2013-1665 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-1665?

CVE-2013-1665 affects the following packages: django (PyPI), django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2013-1665?

Update django to 1.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1665 is resolved across your whole dependency graph.

How do I detect CVE-2013-1665 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-1665 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2013-1665 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-1665 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-1665?

CVE-2013-1665 has an EPSS (Exploit Prediction Scoring System) score of 4.5%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-1665?

CVE-2013-1665 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-1665 published, and has it been updated?

CVE-2013-1665 was published on April 3, 2013 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2013-1665 — django

Fix: django/django@1c60d07

CVE-2013-1665 is a Information Exposure vulnerability in django. A fix is available for django — see the affected versions and patch details below.

XML External Entity (XXE) in Django

Also known asGHSA-x64m-686f-fmm3PYSEC-2026-802

Published

Apr 3, 2013

Updated

Jul 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐍django🐍django

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The XML libraries for Python 3.4, 3.3, 3.2, 3.1, 2.7, and 2.6, 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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django`	≥ 1.3.0&&< 1.3.6	1.3.6`pip install --upgrade 'django==1.3.6'`
🐍PyPI	`django`	≥ 1.4.0&&< 1.4.4	1.4.4`pip install --upgrade 'django==1.4.4'`

Affected Products

2 products · 2 configurations

Application

folsomopenstack

all

Application

keystone essexopenstack

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django to 1.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1665 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This issue affects the versions of python as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates.

Product	Fixed in	Advisory
OpenStack Folsom for RHEL 6	`openstack-keystone-0:2012.2.3-3.el6ost`	RHSA-2013:0596
OpenStack Folsom for RHEL 6	`openstack-nova-0:2012.2.3-4.el6ost`	RHSA-2013:0657
OpenStack Folsom for RHEL 6	`openstack-cinder-0:2012.2.3-4.el6ost`	RHSA-2013:0658
OpenStack Folsom for RHEL 6	`Django14-0:1.4.4-1.el6ost`	RHSA-2013:0670

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-1665 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works