# djust: Client mass-assignment of arbitrary view attributes via the default dj-model update_model handler

Advisory record · `GHSA-cc7c-9jff-58wj`

- **Identifiers:** `GHSA-cc7c-9jff-58wj` · `CVE-2026-61598` · `PYSEC-2026-4042`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-915](https://cwe.mitre.org/data/definitions/915.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 16 Sept 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Sept 2026, 13:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `djust` (PyPI): affected `<1.0.7`; fixed in `1.0.7`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of djust before 1.0.7 let any client over the WebSocket set any public, existing attribute on a LiveView through the default update_model handler, not only fields bound with dj-model. The source describes this as a mass-assignment issue that can reach authorization or ownership state, and an anonymous client can exploit it on public views. Upgrade to djust 1.0.7 or later. Until then, set allowed_model_fields explicitly on views that use dj-model, limited to the fields that should be bindable.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.1 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-cc7c-9jff-58wj)

## Sources

- [GitHub Advisory Database: GHSA-cc7c-9jff-58wj](https://github.com/advisories/GHSA-cc7c-9jff-58wj)
- [OSV: GHSA-cc7c-9jff-58wj](https://osv.dev/vulnerability/GHSA-cc7c-9jff-58wj)
- <https://github.com/djust-org/djust/security/advisories/GHSA-cc7c-9jff-58wj>
- <https://github.com/djust-org/djust>
- <https://github.com/djust-org/djust/releases/tag/v1.0.7>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cc7c-9jff-58wj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cc7c-9jff-58wj/>. Everything for agents: <https://agentprime.io/llms.txt>.
