CVE-2026-61591: CWE-345: Insufficient Verification of Data Authenticity in djust-org djust
djust versions prior to 1.0.7 have a vulnerability where state snapshots embedded in client pages are not integrity-checked. This allows a client to modify unsigned state data such as authorization flags or account information and send it back to the server, potentially escalating privileges or tampering with business state. The issue is fixed in version 1.0.7 by signing state snapshots and rejecting unsigned or forged snapshots on restore. As a workaround, disabling state snapshots or avoiding storing authorization state in public view attributes mitigates the risk.
AI Analysis
Technical Summary
The djust library for Django with Rust-powered reactive server-side rendering had an insufficient verification of data authenticity vulnerability (CWE-345) in versions before 1.0.7. Views that enabled state snapshots embedded an unsigned JSON state in the client page, which was restored on reconnect without integrity checks. This allowed clients to modify the state JSON arbitrarily, such as changing 'is_admin' to true or altering account balances, leading to privilege escalation or business state tampering. The vulnerability is addressed in djust 1.0.7 by signing state snapshots and rejecting unsigned or forged snapshots during back-navigation restore.
Potential Impact
An attacker can manipulate unsigned state snapshots to escalate privileges (e.g., gain admin rights) or alter sensitive business data like account balances. This compromises confidentiality and integrity of application state, potentially leading to unauthorized access and data tampering. There is no indication of availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade to djust version 1.0.7 or later, where state snapshots are signed and unsigned or forged snapshots are rejected. As a temporary workaround, disable state snapshots and avoid storing authorization or ownership information in public view attributes to prevent privilege escalation or state tampering.
CVE-2026-61591: CWE-345: Insufficient Verification of Data Authenticity in djust-org djust
Description
djust versions prior to 1.0.7 have a vulnerability where state snapshots embedded in client pages are not integrity-checked. This allows a client to modify unsigned state data such as authorization flags or account information and send it back to the server, potentially escalating privileges or tampering with business state. The issue is fixed in version 1.0.7 by signing state snapshots and rejecting unsigned or forged snapshots on restore. As a workaround, disabling state snapshots or avoiding storing authorization state in public view attributes mitigates the risk.
CVSS v3.1
Score 8.1high
Affected software
djust-org
djust
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The djust library for Django with Rust-powered reactive server-side rendering had an insufficient verification of data authenticity vulnerability (CWE-345) in versions before 1.0.7. Views that enabled state snapshots embedded an unsigned JSON state in the client page, which was restored on reconnect without integrity checks. This allowed clients to modify the state JSON arbitrarily, such as changing 'is_admin' to true or altering account balances, leading to privilege escalation or business state tampering. The vulnerability is addressed in djust 1.0.7 by signing state snapshots and rejecting unsigned or forged snapshots during back-navigation restore.
Potential Impact
An attacker can manipulate unsigned state snapshots to escalate privileges (e.g., gain admin rights) or alter sensitive business data like account balances. This compromises confidentiality and integrity of application state, potentially leading to unauthorized access and data tampering. There is no indication of availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade to djust version 1.0.7 or later, where state snapshots are signed and unsigned or forged snapshots are rejected. As a temporary workaround, disable state snapshots and avoid storing authorization or ownership information in public view attributes to prevent privilege escalation or state tampering.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-10T17:12:17.237Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aab46e755bf5e2cf58fcc36
Added to database: 09/17/2026, 01:48:23 UTC
Last enriched: 09/17/2026, 02:04:20 UTC
Last updated: 09/17/2026, 04:27:20 UTC
Views: 6
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.