CVE-2026-49222: CWE-639: Authorization Bypass Through User-Controlled Key in givanz Vvveb
Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.4, Vvveb backend product question operations allow a low-privileged Vendor to manage questions under another Vendor's products. The admin/sql/sqlite/product_question.sql queries accept a caller-controlled product_question_id and do not verify product_question.product_id against product.admin_id for the current admin_id. An attacker can read pending question content and moderation data, change question status, edit question content, or delete questions, manipulating product Q&A visibility and integrity. This issue is fixed in version 1.0.8.4.
AI Analysis
Technical Summary
CVE-2026-49222 is an authorization bypass vulnerability in the Vvveb CMS product question management backend. The vulnerability occurs because the SQL queries in admin/sql/sqlite/product_question.sql accept a caller-controlled product_question_id parameter but do not verify that the product_question.product_id belongs to the current admin_id. As a result, a low-privileged vendor can access and manipulate questions under other vendors' products, including reading pending questions and moderation data, changing question status, editing content, or deleting questions. This compromises the integrity and visibility of product Q&A content. The vulnerability affects versions prior to 1.0.8.4 and is resolved in 1.0.8.4.
Potential Impact
An attacker with low privileges as a vendor can bypass authorization controls to access and modify product questions of other vendors. This can lead to unauthorized disclosure of pending question content and moderation data, unauthorized modification or deletion of questions, and manipulation of product Q&A visibility and integrity. The impact includes loss of data integrity, confidentiality of pending moderation content, and potential disruption of product-related communications.
Mitigation Recommendations
This vulnerability is fixed in Vvveb version 1.0.8.4. Users should upgrade to version 1.0.8.4 or later to remediate the issue. No vendor advisory or official patch link was provided, but the fix version is explicitly stated. Until upgrading, restrict vendor privileges or monitor product question management closely to mitigate risk.
CVE-2026-49222: CWE-639: Authorization Bypass Through User-Controlled Key in givanz Vvveb
Description
Vvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.4, Vvveb backend product question operations allow a low-privileged Vendor to manage questions under another Vendor's products. The admin/sql/sqlite/product_question.sql queries accept a caller-controlled product_question_id and do not verify product_question.product_id against product.admin_id for the current admin_id. An attacker can read pending question content and moderation data, change question status, edit question content, or delete questions, manipulating product Q&A visibility and integrity. This issue is fixed in version 1.0.8.4.
CVSS v3.1
Score 7.6high
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-49222 is an authorization bypass vulnerability in the Vvveb CMS product question management backend. The vulnerability occurs because the SQL queries in admin/sql/sqlite/product_question.sql accept a caller-controlled product_question_id parameter but do not verify that the product_question.product_id belongs to the current admin_id. As a result, a low-privileged vendor can access and manipulate questions under other vendors' products, including reading pending questions and moderation data, changing question status, editing content, or deleting questions. This compromises the integrity and visibility of product Q&A content. The vulnerability affects versions prior to 1.0.8.4 and is resolved in 1.0.8.4.
Potential Impact
An attacker with low privileges as a vendor can bypass authorization controls to access and modify product questions of other vendors. This can lead to unauthorized disclosure of pending question content and moderation data, unauthorized modification or deletion of questions, and manipulation of product Q&A visibility and integrity. The impact includes loss of data integrity, confidentiality of pending moderation content, and potential disruption of product-related communications.
Mitigation Recommendations
This vulnerability is fixed in Vvveb version 1.0.8.4. Users should upgrade to version 1.0.8.4 or later to remediate the issue. No vendor advisory or official patch link was provided, but the fix version is explicitly stated. Until upgrading, restrict vendor privileges or monitor product question management closely to mitigate risk.
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: 6a8489bac6e8be03327827f9
Added to database: 08/18/2026, 16:35:06 UTC
Last enriched: 08/18/2026, 16:50:25 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.