CVE-2026-64821: Cross-Site Request Forgery (CSRF) in thiagopena djangoSIGE
djangoSIGE versions up to and including 1.10 contain a cross-site request forgery (CSRF) vulnerability. This flaw allows unauthenticated attackers to trick authenticated users with specific permissions into unintentionally canceling sales or purchase orders. The vulnerability arises because order cancellation actions are handled via HTTP GET requests, which bypass Django's CSRF protections that only apply to unsafe HTTP methods. No official fix or patch is currently documented.
AI Analysis
Technical Summary
The djangoSIGE application through version 1.10 (commit a6fe7e8) is vulnerable to CSRF attacks due to order cancellation logic implemented inside HTTP GET method handlers in views such as CancelarOrcamentoVendaView, CancelarPedidoVendaView, CancelarOrcamentoCompraView, and CancelarPedidoCompraView. Since Django's CsrfViewMiddleware enforces CSRF token validation only on unsafe HTTP methods (e.g., POST, PUT, DELETE), these GET requests can be exploited by attackers who lure authenticated users with the necessary permissions to a malicious page containing cross-origin references to the cancellation endpoints. This allows unauthorized cancellation of sales or purchase orders without the victim's explicit consent.
Potential Impact
An attacker can cause an authenticated user with change_orcamentovenda or equivalent permissions to unknowingly cancel sales or purchase orders. This can disrupt business operations by invalidating legitimate orders. The vulnerability does not require the attacker to be authenticated and bypasses CSRF protections due to misuse of HTTP GET for state-changing operations.
Mitigation Recommendations
No official patch or remediation is currently documented for this vulnerability. Users should avoid using vulnerable versions (<=1.10) or modify the application to ensure that state-changing operations like order cancellations are not handled via HTTP GET requests. Instead, these should be implemented using HTTP methods that enforce CSRF protection, such as POST, along with proper CSRF token validation. Monitor vendor advisories for any forthcoming official fixes.
CVE-2026-64821: Cross-Site Request Forgery (CSRF) in thiagopena djangoSIGE
Description
djangoSIGE versions up to and including 1.10 contain a cross-site request forgery (CSRF) vulnerability. This flaw allows unauthenticated attackers to trick authenticated users with specific permissions into unintentionally canceling sales or purchase orders. The vulnerability arises because order cancellation actions are handled via HTTP GET requests, which bypass Django's CSRF protections that only apply to unsafe HTTP methods. No official fix or patch is currently documented.
CVSS v4.0
Score 5.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The djangoSIGE application through version 1.10 (commit a6fe7e8) is vulnerable to CSRF attacks due to order cancellation logic implemented inside HTTP GET method handlers in views such as CancelarOrcamentoVendaView, CancelarPedidoVendaView, CancelarOrcamentoCompraView, and CancelarPedidoCompraView. Since Django's CsrfViewMiddleware enforces CSRF token validation only on unsafe HTTP methods (e.g., POST, PUT, DELETE), these GET requests can be exploited by attackers who lure authenticated users with the necessary permissions to a malicious page containing cross-origin references to the cancellation endpoints. This allows unauthorized cancellation of sales or purchase orders without the victim's explicit consent.
Potential Impact
An attacker can cause an authenticated user with change_orcamentovenda or equivalent permissions to unknowingly cancel sales or purchase orders. This can disrupt business operations by invalidating legitimate orders. The vulnerability does not require the attacker to be authenticated and bypasses CSRF protections due to misuse of HTTP GET for state-changing operations.
Mitigation Recommendations
No official patch or remediation is currently documented for this vulnerability. Users should avoid using vulnerable versions (<=1.10) or modify the application to ensure that state-changing operations like order cancellations are not handled via HTTP GET requests. Instead, these should be implemented using HTTP methods that enforce CSRF protection, such as POST, along with proper CSRF token validation. Monitor vendor advisories for any forthcoming official fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-20T18:27:48.160Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5fdc239c2644c7f8ba04dc
Added to database: 07/21/2026, 20:52:51 UTC
Last enriched: 07/21/2026, 21:08:10 UTC
Last updated: 07/21/2026, 21:08:11 UTC
Views: 4
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.