Vulnerabilities

Security research · CVE-2025-24370

Django-Unicorn Class Pollution Vulnerability, Leading to XSS, DoS and Authentication Bypass

Published Feb 3, 2025 · catalog updated Oct 27, 2026 · Django-Unicorn Class Pollution Vulnerability,

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-24370. EPSS is 0.49%. Act only if a listed version of Django-Unicorn Class Pollution Vulnerability, is installed.

Severity

Critical—

Known exploitation

Not in CISA/VulnCheck KEV

EPSS

0.49%

Remediation

Advisory link

Affected products

PyPI django-unicorn

# Summary Django-Unicorn is vulnerable to python class pollution vulnerability, a new type of vulnerability categorized under [CWE-915](https://cwe.mitre.org/data/definitions/915.html). The vulnerability arises from the core functionality , 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. At least five ways of vulnerability exploitation have been found, stably resulting in Cross-Site Scripting (XSS), Denial of Service (DoS), and Authentication Bypass attacks in almost every Django-Unicorn-based application. # Analysis of Vulnerable Function By taking a look at the vulnerable function located at: . You can observe the functionality is responsible for modifying a property value of an object. The property is specified by a dotted form of path at the second parameter , where nested reference to object is supported, and base object and the assigned value is given by the first parameter and third parameter . Meanwhile, this functionality can be directly triggered by a component request, one of the core functionalities of the project, by specifying the request type as and payload object would be fed in the dotted-path (2nd) parameter and assigned value (3rd) parameter of the vulnerable function. You are now aware of that users from the remote can fully control the and of the vulnerable function. By default the preperty value overwrite can only be performed on the component object, which is always the first parameter of the function. However, the functionality failed to count in the situation where bad actors can modify the normal path to traverse to other objects in the python runtime, by leveraging the **magic attributes**. For example, if the was set to , the component context would change to global context of the component module, which means you can modify any attributes of the objects that are loc