CVE-2026-61591
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Summary
djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, for views that opt into state snapshots, the snapshot state_json embedded in the client page was restored on reconnect as trusted view state with no integrity check. A client could edit the unsigned state_json in their page and return it in the reconnect mount frame to inject arbitrary view attributes — e.g. flip is_admin to True, or change account_id / balance — escalating privilege or tampering with business state held in public view attributes (the normal djust pattern). This issue is fixed in djust 1.0.7. State snapshots are signed; unsigned or forged snapshots are rejected on the back-navigation restore path. As a workaround, do not enable state snapshots; do not hold authorization/ownership state in public view attributes.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| djust-org | djust | < 1.0.7 | affected |
Weaknesses
- CWE-345: CWE-345: Insufficient Verification of Data Authenticity
- CWE-915: CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes
References
- https://github.com/djust-org/djust/security/advisories/GHSA-c67v-vqrp-m5wj
- https://github.com/djust-org/djust/releases/tag/v1.0.7
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.