🛡️ CVE-2013-0305 — django
Description
Django Data leakage via admin history log
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.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. Rated impact: confidentiality low, integrity none, availability none.
Weakness class
CVE-2013-0305 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-0305 is recorded against 1 package.
- django (from 1.4 up to 1.4.4)
Timeline and source
Published on 5 May 2022 and last revised on 19 February 2025. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Package)
github.com (Web)
www.djangoproject.com (Web)
rhn.redhat.com (Web)
ubuntu.com (Web)
www.debian.org (Web)
Details
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| django | 1.4 | 1.4.4 |
References
Similar Threats
- Unknown CLSA-2025-1753747897
- Unknown CLSA-2025-1754352700
- Unknown CLSA-2025-1754352704
- Unknown CLSA-2025-1754352705
- Unknown CLSA-2025-1755821485
More CVE 2013 advisories
Browse all of CVE 2013 in the advisory index.
Free Vulnerability Check
Is your site affected by CVE-2013-0305?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2013-0305 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.