CVE-2019-19118: Django Unintended Model Editing

django Updated 02 Oct 2025

Summary

04/12/2019

Disclosed on

CVE-2019-19118

CVE

Yes i

Fix available

High

Severity

6.5

CVSS Score

CVE-2019-19118: Django allows unintended model editing. Affects django across 2 version ranges.

>= 2.1, < 2.1.15 >= 2.2, < 2.2.8

Fixed in 2.1.15 or 2.2.8, depending on the release line you run. How to fix ↓

Also tracked for

python-django · Debian:11

The same CVE-2019-19118 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

Django is a popular Python web framework that provides a set of tools and functionalities for building web applications. It allows developers to define models, which represent the data structure of the application, and provides an admin interface for managing and editing these models. However, a vulnerability has been discovered in Django versions 2.1 before 2.1.15 and 2.2 before 2.2.8 that allows unintended model editing.

Vulnerability Detail

The vulnerability in Django occurs when a model admin displays inline related models. In this scenario, if a user has view-only permissions for the parent model but edit permissions for the inline model, they would be presented with an editing user interface. This interface allows the user to make POST requests for updating the inline model. Although directly editing the view-only parent model is not possible, the parent model's save() method is called, which can trigger potential side effects and invoke pre and post-save signal handlers. This vulnerability can lead to unintended changes in the parent model and its associated data.

How To Fix

Latest published version: 6.1.2 as of 22 Oct 2026

pip install --upgrade "django==6.1.2"

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

>= 2.1, < 2.1.15 2.1.15
```
pip install --upgrade "django==2.1.15"
```
>= 2.2, < 2.2.8 2.2.8
```
pip install --upgrade "django==2.2.8"
```

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

In conclusion, the Django framework is vulnerable to unintended model editing in certain versions. It is recommended to upgrade to the fixed versions to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for django →

FAQ

What is the impact of this vulnerability?

This vulnerability allows users with edit permissions on inline models to unintentionally modify the parent model, potentially causing unintended changes and triggering pre and post-save signal handlers.