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).
Fixed in djust 1.0.7. State snapshots are signed; unsigned or forged snapshots are rejected on the back-navigation restore path.
Do not enable state snapshots; do not hold authorization/ownership state in public view attributes.
{
"cwe_ids": [
"CWE-345",
"CWE-915"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-16T21:56:12Z",
"nvd_published_at": null,
"severity": "HIGH"
}