codingjoe django-select2 up to 8.4.0 on Select2 ModelSelect2MultipleWidget/ModelSelect2Widget transmission of private resources into a new sphere ('resource leak')
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in codingjoe django-select2 up to 8.4.0 on Select2. This vulnerability affects the function ModelSelect2MultipleWidget/ModelSelect2Widget. The manipulation leads to transmission of private resources into a new sphere ('resource leak').
This vulnerability is traded as CVE-2025-48383. It is possible to initiate the attack remotely. There is no exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in codingjoe django-select2 up to 8.4.0 on Select2 and classified as critical. This issue affects the function ModelSelect2MultipleWidget/ModelSelect2Widget. The manipulation with an unknown input leads to a transmission of private resources into a new sphere ('resource leak') vulnerability. Using CWE to declare the problem leads to CWE-402. The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2025-48383 since 05/19/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 8.4.1 eliminates this vulnerability. Applying the patch e5f41e6edba004d35f94915ff5e2559f44853412 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Transmission of private resources into a new sphere ('resource leak')CWE: CWE-402
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: django-select2 8.4.1
Patch: e5f41e6edba004d35f94915ff5e2559f44853412
Timeline
05/19/2025 🔍05/27/2025 🔍
05/27/2025 🔍
05/27/2025 🔍
Sources
Product: github.comAdvisory: GHSA-wjrh-hj83-3wh7
Status: Confirmed
CVE: CVE-2025-48383 (🔍)
GCVE (CVE): GCVE-0-2025-48383
GCVE (VulDB): GCVE-100-310379
Entry
Created: 05/27/2025 18:40Changes: 05/27/2025 18:40 (68)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.