Django Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

2.2.028
2.2.128
2.2.227
2.2.326
2.2.422

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix112
Temporary Fix0
Workaround0
Unavailable0
Not Defined14

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High2
Functional0
Proof-of-Concept10
Unproven12
Not Defined102

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local1
Adjacent14
Network111

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High2
Low30
None94

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required38
None88

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤49
≤518
≤648
≤725
≤820
≤95
≤100

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤32
≤410
≤531
≤642
≤726
≤811
≤94
≤100

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤31
≤413
≤525
≤649
≤716
≤822
≤90
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤31
≤41
≤51
≤66
≤710
≤816
≤93
≤107

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤50
≤61
≤70
≤80
≤93
≤101

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k8
<2k7
<5k11
<10k56
<25k43
<50k1
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k105
<2k12
<5k7
<10k2
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (353): 0.1, 0.2, 0.2.1, 0.2.3, 0.3, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.4, 0.5, 0.6, 0.7, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.7.5, 0.7.6, 0.7.7, 0.7.8, 0.8, 0.8.4, 0.9, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6, 0.9.7, 0.9.8, 0.9.9, 0.9.11, 0.9.12, 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.9.17, 0.9.18, 0.9.19, 0.9.21, 0.9.22, 0.9.23, 0.9.24, 0.9.25, 0.9.26, 0.9.27, 0.9.28, 0.9.29, 0.9.31, 0.9.32, 0.9.33, 0.9.34, 0.9.35, 0.9.36, 0.9.37, 0.9.38, 0.9.39, 0.9.41, 0.9.42, 0.9.43, 0.9.44, 0.9.45, 0.9.46, 0.9.47, 0.9.48, 0.9.49, 0.91, 0.95, 0.95.1, 0.96, 1, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.2, 1.1.3, 1.1.4, 1.2, 1.2-alpha1, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.4, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.4.9, 1.4.11, 1.4.12, 1.4.13, 1.4.14, 1.4.15, 1.4.16, 1.4.17, 1.4.18, 1.4.19, 1.4.21, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.6, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5, 1.6.6, 1.6.7, 1.6.8, 1.6.9, 1.7, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8, 1.7.9, 1.8, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, 1.8.7, 1.8.8, 1.8.9, 1.8.11, 1.8.12, 1.8.13, 1.8.14, 1.8.15, 1.8.16, 1.8.17, 1.8.18, 1.9, 1.9.1, 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.9.9, 1.9.11, 1.9.12, 1.10, 1.10.1, 1.10.2, 1.10.3, 1.10.4, 1.10.5, 1.10.6, 1.10.7, 1.10.8, 1.10.9, 1.10.11, 1.10.12, 1.10.13, 1.10.14, 1.10.15, 1.10.16, 1.10.17, 1.10.18, 1.10.19, 1.10.21, 1.10.22, 1.10.23, 1.10.24, 1.10.25, 1.10.26, 1.10.27, 1.10.28, 1.11, 1.11.1, 1.11.2, 1.11.3, 1.11.4, 1.11.5, 1.11.6, 1.11.7, 1.11.8, 1.11.9, 1.11.11, 1.11.12, 1.11.13, 1.11.14, 1.11.15, 1.11.16, 1.11.17, 1.11.18, 1.11.19, 1.11.21, 1.11.22, 1.11.23, 1.11.24, 1.11.25, 1.11.26, 1.11.27, 2, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 2.1.8, 2.1.9, 2.1.11, 2.1.12, 2.1.13, 2.1.14, 2.2, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 2.2.9, 2.2.11, 2.2.12, 2.2.13, 2.2.14, 2.2.15, 2.2.16, 2.2.17, 2.2.18, 2.2.19, 2.2.21, 2.2.22, 2.2.23, 2.2.24, 2.2.25, 2.2.26, 2.2.27, 2.3, 2.4, 2.5, 2.6, 3, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.0.7, 3.0.8, 3.0.9, 3.0.11, 3.0.12, 3.0.13, 3.1, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7, 3.1.8, 3.1.9, 3.1.11, 3.1.12, 3.1.13, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.8, 3.2.9, 3.2.11, 3.2.12, 3.2.13, 3.2.14, 3.2.15, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.11, 3.11.1, 4, 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 4.1, 4.1.1, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 12.0, 12.1, 12.2, 12.3

Software Type: Content Management System

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
10/16/20225.55.4Django URL incorrect regex$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-41323
10/11/20226.96.7django-mfa2 Device Registration FIDO2.py authentication replay$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-42731
08/04/20223.53.4Django Header FileResponse information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-36359
07/23/20224.84.7Django REST Framework DRF Browsable API cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2018-25045
07/05/20228.07.9KDE Django Extract sql injection$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-34265
06/25/20227.77.7django-navbar-client Request Package backdoor$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2022-32996
06/09/20228.28.0django-s3file AWS S3 Bucket path traversal$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-24840
04/15/20225.55.3django-mfa3 improper authentication$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-24857
04/12/20226.36.0Django Dictionary QuerySet.explain sql injection$5k-$25k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-28347
04/12/20226.36.0Django QuerySet.aggregate sql injection$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-28346
02/03/20223.53.4Django Debug Template Tag cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-22818
02/03/20223.53.4Django Multipart Form infinite loop$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-23833
01/05/20225.55.3Django Filename Storage.save pathname traversal$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-45452
01/05/20223.53.4Django Template Language information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2021-45116
01/05/20223.53.4Django User Registration UserAttributeSimilarityValidator denial of service$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-45115
12/09/20214.64.4Apache Airavata Django Portal HTTP Request Parameter neutralization for logs$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-43410
12/08/20217.37.0Django HTTP Request access control$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-44420
12/01/20217.67.5django-helpdesk Web Page Generation cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-3994
11/24/20214.44.4Django-wiki Notification Section cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-25986
11/19/20216.56.4django-helpdesk Web Page Generation cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2021-3950
11/13/20216.56.4django-helpdesk Web Page Generation cross site scripting$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2021-3945
08/17/20216.36.3Django-Widgy Change Widgy Page unrestricted upload$0-$5k$0-$5kNot DefinedNot Defined0.05CVE-2020-18704
07/02/20216.36.0Django QuerySet.order_by sql injection$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2021-35042
06/09/20215.55.3Django pathname traversal$5k-$25k$0-$5kNot DefinedOfficial Fix0.07CVE-2021-33203
06/09/20215.55.3Django validate_ipv46_address access control$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2021-33571

101 more entries are not shown

Do you know our Splunk app?

Download it now for free!