CVE-2025-48383 | Django-Select2 Vulnerable to Widget Instance Secret Cache Key Leaking

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.

Published: 2025-05-27 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-48383 is rated Moderate Risk (51.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.29%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-48383

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-23 0.05% 0.29% +0.24%
2 2025-12-21 0.05% 0.05% +0.01%
3 2025-11-21 — 0.05% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-48383

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 4.2 [email protected]

Weakness enumeration for CVE-2025-48383

GitHub Security Advisory for CVE-2025-48383

GHSA-wjrh-hj83-3wh7 · Severity: high · Ecosystem: pip — Django-Select2 Vulnerable to Widget Instance Secret Cache Key Leaking

OS Trackers for CVE-2025-48383

vendor priority summary link
debian not yet assigned CVE-2025-48383 not yet assigned priority: Debian including 1 source packages (django-select2), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2025-48383
ubuntu medium CVE-2025-48383 medium priority: Ubuntu including 1 source packages (django-select2), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): needs-triage 4, ignored 2, DNE 1. https://ubuntu.com/security/CVE-2025-48383

Affected software / configurations for CVE-2025-48383

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-48383

cvelogic Threat Intelligence