---
title: "CVE-2025-24370: Django-Unicorn Class Pollution Vulnerability, Leading to XSS, DoS and Authentication Bypass"
url: https://erroneo.us/security/cve/CVE-2025-24370/
description: "CVE-2025-24370 (django-unicorn (PyPI)): Django-Unicorn adds modern reactive component functionality to Django templates. Affected versions of Django-Unicorn…"
type: vulnerability-record
section: "Security Digest"
date_published: 2025-02-03
date_modified: 2025-05-08
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2025-24370"
kev: false
cvss: 9.3
epss: 0.00492
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2025-24370: Django-Unicorn Class Pollution Vulnerability, Leading to XSS, DoS and Authentication Bypass

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.5% , percentile 41: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 41% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes django-unicorn (PyPI) < 0.62.0, fixed in 0.62.0 . Check your lockfile, including transitive dependencies.

## What it is

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 setpropertyvalue, 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.

## Affected packages

- PyPI `django-unicorn` < 0.62.0 → fixed: 0.62.0

## Affected products (CVE record)

- adamghill django-unicorn: < 0.62.0

## Severity

- GitHub_M CVSS 4.0: 9.3 `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`
- GitHub CVSS 4.0: 9.3 `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`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.49% probability of exploitation activity in the next 30 days; percentile 41.

## Sources

- [GitHub Advisory GHSA-g9wf-5777-gq43](https://github.com/advisories/GHSA-g9wf-5777-gq43)
- [CVE.org record CVE-2025-24370](https://www.cve.org/CVERecord?id=CVE-2025-24370)
- [NVD entry CVE-2025-24370](https://nvd.nist.gov/vuln/detail/CVE-2025-24370)
- [github.com](https://github.com/adamghill/django-unicorn/security/advisories/GHSA-g9wf-5777-gq43)
- [github.com](https://github.com/adamghill/django-unicorn/commit/17614200f27174f789d4af54cc3a1f2b0df7870c)
- [github.com](https://github.com/adamghill/django-unicorn/releases/tag/0.62.0)

---
Source page: https://erroneo.us/security/cve/CVE-2025-24370/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt