Django Software Foundation up to 5.2.18/6.0.9/6.1.2 Geometry Widget widgets.py neutralization for logs

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Django Software Foundation Django up to 5.2.18/6.0.9/6.1.2. Affected by this issue is the function django.contrib.gis.forms.widgets.BaseGeometryWidget.deserialize of the file django/contrib/gis/forms/widgets.py of the component Geometry Widget. Performing a manipulation results in neutralization for logs. This vulnerability is identified as CVE-2026-111211. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Django Software Foundation Django up to 5.2.18/6.0.9/6.1.2. It has been classified as problematic. This affects the function django.contrib.gis.forms.widgets.BaseGeometryWidget.deserialize of the file django/contrib/gis/forms/widgets.py of the component Geometry Widget. The manipulation with an unknown input leads to a neutralization for logs vulnerability. CWE is classifying the issue as CWE-117. The product does not neutralize or incorrectly neutralizes output that is written to logs. This is going to have an impact on integrity. The summary by CVE is:

An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. `django.contrib.gis.forms.widgets.BaseGeometryWidget.deserialize()`, used by `django.contrib.gis.forms.GeometryField`, does not escape invalid submitted values before logging them, which allows remote attackers to inject or forge log entries via a crafted geometry value. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Aaron chen for reporting this issue.

It is possible to read the advisory at docs.djangoproject.com. This vulnerability is uniquely identified as CVE-2026-111211 since 10/15/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/03/2026).

Upgrading to version 5.2.19, 6.0.10 or 6.1.3 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Django Software Foundation

Name

• Django

Version

• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.2.7
• 5.2.8
• 5.2.9
• 5.2.10
• 5.2.11
• 5.2.12
• 5.2.13
• 5.2.14
• 5.2.15
• 5.2.16
• 5.2.17
• 5.2.18
• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.1.0
• 6.1.1
• 6.1.2

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion