Authenticated cart reuse via unchecked checkout identifier
Published May 15, 2026 · Updated May 15, 2026
Authorization bypass in givanz Vvveb before 1.0.8.3 allows remote authenticated users to reuse another user's cart during checkout. The checkout route loads the cart named by the URL cart_id and checks only that it contains products, without binding the cart to the current user or session. Any logged-in user who obtains a predictable cart identifier can feed that cart state into a valid checkout flow, affecting order creation, totals, and downstream business logic.
Summary
What happened
Authorization bypass in givanz Vvveb before 1.0.8.3 allows remote authenticated users to reuse another user's cart during checkout. The checkout route loads the cart named by the URL cart_id and checks only that it contains products, without binding the cart to the current user or session. Any logged-in user who obtains a predictable cart identifier can feed that cart state into a valid checkout flow, affecting order creation, totals, and downstream business logic.
The record
- CVE
- CVE-2026-46408
- Published
- May 15, 2026
- Updated
- May 15, 2026
- Vendor
- givanz
- Product
- Vvveb
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- May 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.8.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream authenticated checkout proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo