Skip to content
Fencer Intel
medium 4.3

CVE-2013-0305 json

Django Data leakage via admin history log

published 13y ago modified 4mo ago also GHSA-r7w6-p47g-vj53 , PYSEC-2013-16 , EUVD-2013-0004

cvss
4.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

The administrative interface for Django 1.3.x before 1.3.6, 1.4.x before 1.4.4, and 1.5 before release candidate 2 does not check permissions for the history view, which allows remote authenticated administrators to obtain sensitive object history information.

Patch / fix

  • pypi django 1.3.6, 1.4.4
  • python-django Debian 14, Debian 13, Debian 12 1.4.4-1

debian advisories DEBIAN-CVE-2013-0305

  • Django14 openstack 2 1.4.4-1.el6ost

red hat advisories RHSA-2013:0670

Is CVE-2013-0305 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-0305 updated cvss 4.0

Django: Data leakage via admin history log

  • Red Hat Subscription Asset Manager Django
    affected: no fix available
  • Red Hat OpenStack Folsom Django14 1.4.4-1.el6ost
    fixed: vendor fix RHSA-2013:0670

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.86% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi django
>=1.3, <1.3.6
>=1.4, <1.4.4
1.3.6
1.4.4

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.