CVE-2026-4277: CWE-862: Missing Authorization in djangoproject Django
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank N05ec@LZU-DSLab for reporting this issue.
AI Analysis
Technical Summary
CVE-2026-4277 is a missing authorization vulnerability (CWE-862) in the Django web framework affecting versions 6.0 prior to 6.0.4, 5.2 prior to 5.2.13, and 4.2 prior to 4.2.30. The flaw occurs because Django's GenericInlineModelAdmin does not validate permissions on inline model instances when processing forged POST requests, potentially allowing unauthorized data manipulation. Earlier unsupported versions such as 5.0.x, 4.1.x, and 3.2.x may also be vulnerable but were not assessed. The vulnerability is rated critical with a CVSS 3.1 base score of 9.8, reflecting network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. No official patch or remediation level is documented in the provided information, and no known exploits have been observed in the wild.
Potential Impact
Successful exploitation of this vulnerability could allow an attacker to bypass authorization controls and manipulate inline model data within Django admin interfaces. This could lead to unauthorized data modification, disclosure, or deletion, severely impacting the confidentiality, integrity, and availability of affected Django applications. The CVSS score of 9.8 underscores the critical nature of this issue. However, no known exploits have been reported to date.
Mitigation Recommendations
Patch status is not yet confirmed — check the official Django project advisory for current remediation guidance. Until an official fix is available, administrators should consider restricting access to Django admin interfaces and carefully validate user permissions to mitigate potential exploitation. Monitor Django project communications for updates on patches or official fixes.
CVE-2026-4277: CWE-862: Missing Authorization in djangoproject Django
Description
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank N05ec@LZU-DSLab for reporting this issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-4277 is a missing authorization vulnerability (CWE-862) in the Django web framework affecting versions 6.0 prior to 6.0.4, 5.2 prior to 5.2.13, and 4.2 prior to 4.2.30. The flaw occurs because Django's GenericInlineModelAdmin does not validate permissions on inline model instances when processing forged POST requests, potentially allowing unauthorized data manipulation. Earlier unsupported versions such as 5.0.x, 4.1.x, and 3.2.x may also be vulnerable but were not assessed. The vulnerability is rated critical with a CVSS 3.1 base score of 9.8, reflecting network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. No official patch or remediation level is documented in the provided information, and no known exploits have been observed in the wild.
Potential Impact
Successful exploitation of this vulnerability could allow an attacker to bypass authorization controls and manipulate inline model data within Django admin interfaces. This could lead to unauthorized data modification, disclosure, or deletion, severely impacting the confidentiality, integrity, and availability of affected Django applications. The CVSS score of 9.8 underscores the critical nature of this issue. However, no known exploits have been reported to date.
Mitigation Recommendations
Patch status is not yet confirmed — check the official Django project advisory for current remediation guidance. Until an official fix is available, administrators should consider restricting access to Django admin interfaces and carefully validate user permissions to mitigate potential exploitation. Monitor Django project communications for updates on patches or official fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- DSF
- Date Reserved
- 2026-03-16T15:26:08.125Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d51c3eaaed68159a2c162a
Added to database: 4/7/2026, 3:01:18 PM
Last enriched: 4/15/2026, 12:22:14 PM
Last updated: 5/23/2026, 9:58:12 PM
Views: 87
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.