# CVE-2026-64821: djangoSIGE 1.10 CSRF via GET-based Order Cancellation Views

> Unauthenticated attackers can cancel sales or purchase orders on behalf of authenticated users via CSRF in djangoSIGE.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-83g7-qjjj-48pv

## What is CVE-2026-64821?

CVE-2026-64821 is a medium-severity vulnerability in thiagopena djangoSIGE, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

djangoSIGE through 1.10 (commit a6fe7e8) contains a cross-site request forgery vulnerability that allows unauthenticated attackers to cancel sales or purchase orders on behalf of authenticated users by exploiting order-cancellation logic implemented inside HTTP GET method handlers in CancelarOrcamentoVendaView, CancelarPedidoVendaView, CancelarOrcamentoCompraView, and CancelarPedidoCompraView. Attackers can lure an authenticated victim with change_orcamentovenda or equivalent permissions to a page containing a cross-origin reference such as an img tag pointing to the cancellation endpoint, bypassing CSRF token validation entirely since Django's CsrfViewMiddleware only enforces CSRF checks on unsafe HTTP methods.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-64821?


## How do I fix CVE-2026-64821?

No fix has been published for CVE-2026-64821 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-64821 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64821 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64821 and fix it if it is affected.

What it is: CVE-2026-64821 is a medium-severity vulnerability in thiagopena djangoSIGE, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64821 exists.

Affected product: thiagopena djangoSIGE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64821/ (Markdown: https://insights.sbomify.com/CVE-2026-64821/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64821
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64821
- OSV: https://osv.dev/vulnerability/CVE-2026-64821

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64821/
Summaries are generated and may contain mistakes; the official description above is the record.