{"answers":{"affected":"5 open source packages ship an affected version, including django and Django. It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-19118 in the wild and no public exploit code.","fix":"Upgrade django to a fixed version for your release line: 2.1.15 or 2.2.8.","what":"CVE-2019-19118 is a medium-severity missing authorization vulnerability in Djangoproject Django, published on 2 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19118 and fix it if it is affected.\n\nWhat it is: CVE-2019-19118 is a medium-severity missing authorization vulnerability in Djangoproject Django, published on 2 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-19118 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django (PyPI): affected from 2.1; fixed in 2.1.15, 2.2.8\n- django (PyPI): affected from 2.1; fixed in 2.1.15\n- django (PyPI): affected from 2.2; fixed in 2.2.8\n- Django (PyPI): affected from 2.1; fixed in 2.1.15\n- Django (PyPI): affected from 2.2; fixed in 2.2.8\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-2019-19118/ (Markdown: https://insights.sbomify.com/CVE-2019-19118/index.md)","id":"CVE-2019-19118","markdown":"https://insights.sbomify.com/CVE-2019-19118/index.md","name":"CVE-2019-19118","record":{"aliases":["DEBIAN-CVE-2019-19118","GHSA-hvmf-r92r-27hr","PYSEC-2019-15"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Django web framework","requires_auth":"low_privilege","summary":"Attackers with view-only parent permissions can trigger side effects and modify inline models via Django admin, bypassing intended access controls.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"django","vendor":"djangoproject"},{"product":"fedora","vendor":"fedoraproject"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"Django 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model editing. A Django model admin displaying inline related models, where the user has view-only permissions to a parent model but edit permissions to the inline model, would be presented with an editing UI, allowing POST requests, for updating the inline model. Directly editing the view-only parent model was not possible, but the parent model's save() method was called, triggering potential side effects, and causing pre and post-save signal handlers to be invoked. (To resolve this, the Django admin is adjusted to require edit permissions on the parent model in order for inline models to be editable.)","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 allows unintended model editing","id":"CVE-2019-19118","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"djangoproject:django","products":["djangoproject:django","fedoraproject:fedora"],"type":"missing_authorization","year":"2019"},"n_packages":5,"n_references":7,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-19119"},"packages":[{"ecosystem":"PyPI","fixed":["2.1.15"],"introduced":["2.1"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-hvmf-r92r-27hr"},{"ecosystem":"PyPI","fixed":["2.2.8"],"introduced":["2.2"],"last_affected":[],"package":"Django","purl":null,"source":"GHSA-hvmf-r92r-27hr"},{"ecosystem":"PyPI","fixed":["2.1.15","2.2.8"],"introduced":["2.1","2.2"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"PYSEC-2019-15"},{"ecosystem":"PyPI","fixed":["2.1.15"],"introduced":["2.1"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-hvmf-r92r-27hr"},{"ecosystem":"PyPI","fixed":["2.2.8"],"introduced":["2.2"],"last_affected":[],"package":"django","purl":"pkg:pypi/django","source":"GHSA-hvmf-r92r-27hr"}],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-19117"},"products":["n/a"],"published":"2019-12-02","related":[{"cvss_score":9.8,"headline":"Privilege abuse in GenericInlineModelAdmin","id":"CVE-2026-4277","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Django SQL injection in HasKey(lhs, rhs) on Oracle","id":"CVE-2024-53908","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.8,"headline":"Django SQL injection vulnerability","id":"CVE-2024-42005","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"Django bypasses validation when using one form field to upload multiple files","id":"CVE-2023-31047","kev_date_added":null,"published":"2023-05-07"},{"cvss_score":9.8,"headline":"Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection","id":"CVE-2022-34265","kev_date_added":null,"published":"2022-07-04"},{"cvss_score":9.8,"headline":"SQL Injection in Django","id":"CVE-2021-35042","kev_date_added":null,"published":"2021-07-02"},{"cvss_score":9.8,"headline":"SQL injection in Django","id":"CVE-2020-7471","kev_date_added":null,"published":"2020-02-03"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers with view-only parent permissions can trigger side effects and modify inline models via Django admin, bypassing intended access controls.","url":"https://insights.sbomify.com/CVE-2019-19118/"}