CVE-2026-49224: CWE-639: Authorization Bypass Through User-Controlled Key in givanz Vvveb
Vvveb CMS versions prior to 1.0.8.4 contain an authorization bypass vulnerability in the backend post revision operations. Low-privileged Authors can access, restore, or delete post revisions belonging to other Authors due to improper validation of user-controlled parameters without enforcing the current admin_id. This can lead to unauthorized disclosure of draft content, corruption of published posts, and removal of audit history. The issue is resolved in version 1.0.8.4.
AI Analysis
Technical Summary
CVE-2026-49224 is an authorization bypass vulnerability in Vvveb CMS before version 1.0.8.4. The backend post revision controller and associated SQLite queries trust user-supplied post_id, language_id, and created_at parameters without consistently verifying the current admin_id. This flaw allows a low-privileged Author to read, restore, or delete revisions of posts owned by other Authors, exposing sensitive draft content, corrupting live posts, and deleting revision audit trails. The vulnerability is classified under CWE-639 (Authorization Bypass Through User-Controlled Key) and has a CVSS 3.1 base score of 8.3, indicating high severity. The issue is fixed in version 1.0.8.4.
Potential Impact
An attacker with low privileges can access and manipulate post revisions of other users, leading to unauthorized disclosure of unpublished content, potential corruption of published posts by restoring unauthorized revisions, and deletion of revision history which undermines audit integrity. This compromises confidentiality, integrity, and partially availability of post content within the CMS.
Mitigation Recommendations
Upgrade Vvveb to version 1.0.8.4 or later, where this authorization bypass vulnerability is fixed. There is no official patch advisory provided, but the fix is included starting from version 1.0.8.4. Until upgrading, restrict Author-level access to trusted users and monitor for suspicious revision activity.
CVE-2026-49224: CWE-639: Authorization Bypass Through User-Controlled Key in givanz Vvveb
Description
Vvveb CMS versions prior to 1.0.8.4 contain an authorization bypass vulnerability in the backend post revision operations. Low-privileged Authors can access, restore, or delete post revisions belonging to other Authors due to improper validation of user-controlled parameters without enforcing the current admin_id. This can lead to unauthorized disclosure of draft content, corruption of published posts, and removal of audit history. The issue is resolved in version 1.0.8.4.
CVSS v3.1
Score 8.3high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-49224 is an authorization bypass vulnerability in Vvveb CMS before version 1.0.8.4. The backend post revision controller and associated SQLite queries trust user-supplied post_id, language_id, and created_at parameters without consistently verifying the current admin_id. This flaw allows a low-privileged Author to read, restore, or delete revisions of posts owned by other Authors, exposing sensitive draft content, corrupting live posts, and deleting revision audit trails. The vulnerability is classified under CWE-639 (Authorization Bypass Through User-Controlled Key) and has a CVSS 3.1 base score of 8.3, indicating high severity. The issue is fixed in version 1.0.8.4.
Potential Impact
An attacker with low privileges can access and manipulate post revisions of other users, leading to unauthorized disclosure of unpublished content, potential corruption of published posts by restoring unauthorized revisions, and deletion of revision history which undermines audit integrity. This compromises confidentiality, integrity, and partially availability of post content within the CMS.
Mitigation Recommendations
Upgrade Vvveb to version 1.0.8.4 or later, where this authorization bypass vulnerability is fixed. There is no official patch advisory provided, but the fix is included starting from version 1.0.8.4. Until upgrading, restrict Author-level access to trusted users and monitor for suspicious revision activity.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-28T03:42:34.341Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a8489bac6e8be03327827fd
Added to database: 08/18/2026, 16:35:06 UTC
Last enriched: 08/18/2026, 16:50:05 UTC
Last updated: 08/18/2026, 18:17:11 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.