Skip to content
Fencer Intel
medium 5.3

CVE-2013-0306 json

Django is vulnerable to Denial of Service attack in formset

published 2013-05-02 13 y ago modified 2026-06-16 4 mo ago also GHSA-g8xg-jgj6-49r3 , PYSEC-2013-17 , EUVD-2013-0005

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

Summary

The form library in Django 1.3.x before 1.3.6, 1.4.x before 1.4.4, and 1.5 before release candidate 2 allows remote attackers to bypass intended resource limits for formsets and cause a denial of service (memory consumption) or trigger server errors via a modified max_num parameter.

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-0306

  • Django14 openstack 2 1.4.4-1.el6ost

red hat advisories RHSA-2013:0670

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-0306 updated cvss 5.0

Django: Formset denial-of-service

  • 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

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

CVSS scores

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

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
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.