GitHub Advisoryadvisory · PyPI

GHSA-wjrh-hj83-3wh7 Django-Select2 Vulnerable to Widget Instance Secret Cache Key Leaking

HIGH Published 2025-05-27 Modified 2025-05-27 Official page ↗
Aliases
CVE-2025-48383
Ecosystem
PyPI
Packages
django-select2
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Weaknesses
CWE-402, CWE-918
Reviewed
2025-05-27

Affected packages

• PyPI django-select2: < 8.4.1 → fixed in 8.4.1

Description

Impact Instances of `HeavySelect2Mixin` subclasses like the `ModelSelect2MultipleWidget` and `ModelSelect2Widget` can secret access tokens across requests. This can allow users to access restricted querysets and restricted data. Patches The problem has been patched in version 8.4.1 and all following versions. Workarounds This vulnerability is limited use cases where instances of widget classes are created during app loading (not during a request). Example of affected code: ```python class MyForm(forms.ModelForm): class Meta: widgets = {"my_select_field": Select2ModelWidget()} ``` Django allows you to pass just the widget class (not the instance). This can be used to mitigate the session request leak. Example of affected code: ```python class MyForm(forms.ModelForm): class Meta: widgets = {"my_select_field": Select2ModelWidget} ``` References Thanks to @neartik for reporting this issue. I will address it later. I had to delete your issue, to avoid exploitation of this security issue.

Related

Alias · CVE (1)

  • CVE-2025-48383 Django-Select2 is a Django integration for Select2. vulnerability

Weakness · CWE (2)

  • CWE-402 Transmission of Private Resources into a New Sphere weakness
  • CWE-918 Server-Side Request Forgery weakness

References