{"answers":{"affected":"3 open source packages ship an affected version, including django-select2.","exploited":"There is no known exploitation of CVE-2025-48383 in the wild and no public exploit code.","fix":"Upgrade django-select2 to 8.4.1 or later.","what":"CVE-2025-48383 is a high-severity vulnerability in codingjoe django-select2, published on 27 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48383 and fix it if it is affected.\n\nWhat it is: CVE-2025-48383 is a high-severity vulnerability in codingjoe django-select2, published on 27 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48383 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-select2 (PyPI): affected all versions; fixed in 8.4.1\n- django-select2 (PyPI): affected all versions; fixed in 8.4.1\n- django-select2 (PyPI): affected all versions; fixed in 8.4.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-48383/ (Markdown: https://insights.sbomify.com/CVE-2025-48383/index.md)","id":"CVE-2025-48383","markdown":"https://insights.sbomify.com/CVE-2025-48383/index.md","name":"CVE-2025-48383","record":{"aliases":["DEBIAN-CVE-2025-48383","GHSA-wjrh-hj83-3wh7","PYSEC-2026-1300","UBUNTU-CVE-2025-48383"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django integration library","requires_auth":"none","summary":"Attackers can leak secret access tokens from widget instances, allowing unauthorized access to restricted data and query sets in Django applications.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-402","name":"Transmission of Private Resources into a New Sphere"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Django-Select2 Vulnerable to Widget Instance Secret Cache Key Leaking","id":"CVE-2025-48383","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Git Link Following","id":"CVE-2025-48384"},"packages":[{"ecosystem":"PyPI","fixed":["8.4.1"],"introduced":["0"],"last_affected":[],"package":"django-select2","purl":null,"source":"GHSA-wjrh-hj83-3wh7"},{"ecosystem":"PyPI","fixed":["8.4.1"],"introduced":["0"],"last_affected":[],"package":"django-select2","purl":"pkg:pypi/django-select2","source":"GHSA-wjrh-hj83-3wh7"},{"ecosystem":"PyPI","fixed":["8.4.1"],"introduced":["0"],"last_affected":[],"package":"django-select2","purl":"pkg:pypi/django-select2","source":"PYSEC-2026-1300"}],"prev":{"headline":"Fess has Insecure Temporary File Permissions","id":"CVE-2025-48382"},"products":["django-select2"],"published":"2025-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-27","vendors":["codingjoe"]},"summary":"Attackers can leak secret access tokens from widget instances, allowing unauthorized access to restricted data and query sets in Django applications.","url":"https://insights.sbomify.com/CVE-2025-48383/"}