CVE-2025-48383: codingjoe django-select2 · Resource Leak
Affects codingjoe django-select2Source CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 8.4.1 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade codingjoe django-select2 to 8.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIdjango-select2pkg:pypi/django-select2Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately audit their Django applications to identify usage of django-select2 versions prior to 8.4.1. The primary mitigation is to upgrade django-select2 to version 8.4.1 or later, where the vulnerability is patched. Additionally, organizations should review and harden access controls around sensitive query sets to minimize impact in case of token leakage. Implementing strict session management and token lifecycle policies can reduce the risk of token reuse or leakage. Conduct code reviews to ensure no custom widgets or mixins replicate similar token handling flaws. Employ web application firewalls (WAFs) with rules to detect anomalous requests targeting select2 widgets. Monitoring and logging access patterns to detect unusual queries or data access attempts is recommended. Finally, organizations should prepare incident response plans to quickly address any detected exploitation attempts.
Description
Django-Select2 is a Django integration for Select2. Prior to version 8.4.1, instances of HeavySelect2Mixin subclasses like the ModelSelect2MultipleWidget and ModelSelect2Widget can leak secret access tokens across requests. This can allow users to access restricted query sets and restricted data. This issue has been patched in version 8.4.1.