CVE-2026-46408
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVvveb is a powerful and easy to use CMS with page builder to build websites, blogs or ecommerce stores. Prior to 1.0.8.3, the checkout endpoint accepts a user-controlled cart_id and uses it to enter the payment flow without verifying cart ownership. A logged-in attacker can therefore reuse another user's cart data in their own checkout session. This vulnerability is fixed in 1.0.8.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe checkout endpoint in Vvveb CMS prior to version 1.0.8.3 accepts a user-supplied cart_id parameter without validating cart ownership, allowing any authenticated user to access and checkout with another user's shopping cart data. This IDOR vulnerability enables unauthorized access to sensitive cart information including potential payment and shipping details.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Vvveb CMS installation versionLocate the version file or admin interface version display. Common locations include a version.php file, admin dashboard footer, or composer.json in the web root. Compare the installed version to 1.0.8.3.Affected if Installed version is below 1.0.8.3 (e.g., 1.0.8.2, 1.0.7.x, etc.)
-
Confirm checkout functionality existsCheck if the application has shopping cart and checkout functionality by examining the URL structure for endpoints like /checkout, /cart, or /order. Look for forms or API endpoints that process cart data.Affected if Checkout endpoint exists and accepts cart_id parameter without ownership verification
-
Verify authenticated user access modelExamine the application authentication system to confirm it allows user accounts with separate shopping carts. Check if session management identifies individual users.Affected if Multiple user accounts can exist and each has an associated shopping cart
-
Test cart_id parameter handling in checkoutWith an authenticated user account, attempt to modify the cart_id parameter in the checkout request to a value belonging to a different user. Observe if the application accepts the cart without verifying ownership.Affected if A user can access another user's cart by manipulating the cart_id parameter in the checkout request
A defender is affected if running Vvveb CMS version prior to 1.0.8.3 AND the checkout endpoint is accessible to authenticated users, allowing cart_id parameter manipulation to access other users' carts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Vvveb version 1.0.8.3 or later, which implements proper cart ownership verification in the checkout flow to ensure users can only access their own carts.
1.0.8.3
- Backup the current Vvveb installation and database before any upgrade
- Upgrade Vvveb to version 1.0.8.3 or later
- Test the checkout flow to confirm cart ownership is now properly validated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46408 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46408 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data