{"answers":{"affected":"3 open source packages ship an affected version, including django-unicorn.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24370 exists.","fix":"Upgrade django-unicorn to 0.62.0 or later.","what":"CVE-2025-24370 is a critical code injection vulnerability in adamghill django-unicorn, published on 3 Feb 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-24370 and fix it if it is affected.\n\nWhat it is: CVE-2025-24370 is a critical code injection vulnerability in adamghill django-unicorn, published on 3 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-24370 exists.\n\nAffected packages and fixed versions:\n- django-unicorn (PyPI): affected all versions; fixed in 0.62.0\n- django-unicorn (PyPI): affected all versions; fixed in 0.62.0\n- django-unicorn (PyPI): affected all versions; fixed in 0.62.0\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-24370/ (Markdown: https://insights.sbomify.com/CVE-2025-24370/index.md)","id":"CVE-2025-24370","markdown":"https://insights.sbomify.com/CVE-2025-24370/index.md","name":"CVE-2025-24370","record":{"aliases":["GHSA-g9wf-5777-gq43","PYSEC-2026-329"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Django reactive components","requires_auth":"none","summary":"Attackers can exploit class pollution in Django-Unicorn to achieve code execution, bypass authentication, or cause denial of service.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-915","name":"Improperly Controlled Modification of Dynamically-Determined Object Attributes"}],"description":"Django-Unicorn adds modern reactive component functionality to Django templates. Affected versions of Django-Unicorn are vulnerable to python class pollution vulnerability. The vulnerability arises from the core functionality `set_property_value`, which can be remotely triggered by users by crafting appropriate component requests and feeding in values of second and third parameter to the vulnerable function, leading to arbitrary changes to the python runtime status. With this finding at least five ways of vulnerability exploitation have been observed, stably resulting in Cross-Site Scripting (XSS), Denial of Service (DoS), and Authentication Bypass attacks in almost every Django-Unicorn-based application. This issue has been addressed in version 0.62.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Django-Unicorn Class Pollution Vulnerability, Leading to XSS, DoS and Authentication Bypass","id":"CVE-2025-24370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Malicious peer can make node stuck in blocksync in github.com/cometbft/cometbft","id":"CVE-2025-24371"},"packages":[{"ecosystem":"PyPI","fixed":["0.62.0"],"introduced":["0"],"last_affected":[],"package":"django-unicorn","purl":null,"source":"GHSA-g9wf-5777-gq43"},{"ecosystem":"PyPI","fixed":["0.62.0"],"introduced":["0"],"last_affected":[],"package":"django-unicorn","purl":"pkg:pypi/django-unicorn","source":"GHSA-g9wf-5777-gq43"},{"ecosystem":"PyPI","fixed":["0.62.0"],"introduced":["0"],"last_affected":[],"package":"django-unicorn","purl":"pkg:pypi/django-unicorn","source":"PYSEC-2026-329"}],"prev":{"headline":"Anubis has a bot protection bypass when a sophisticated attacker asks to pass a challenge of difficulty 0","id":"CVE-2025-24369"},"products":["django-unicorn"],"published":"2025-02-03","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-04","vendors":["adamghill"]},"summary":"Attackers can exploit class pollution in Django-Unicorn to achieve code execution, bypass authentication, or cause denial of service.","url":"https://insights.sbomify.com/CVE-2025-24370/"}