No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 18 Aug 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 18 Aug 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Givanz
Givanz vvveb |
|
| Vendors & Products |
Givanz
Givanz vvveb |
Tue, 18 Aug 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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 digital asset operations allow a low-privileged Vendor to access digital assets linked to another Vendor's products. The admin/controller/product/digital-asset.php and admin/controller/product/digital-assets.php controllers and the admin/sql/sqlite/digital_asset.sql data queries use a caller-controlled digital_asset_id without consistently enforcing the current admin_id ownership boundary. An attacker can list assets, read asset names and file metadata, edit asset metadata, or delete asset records, which can disclose private product metadata, corrupt resource links, and cause data loss. This issue is fixed in version 1.0.8.4. | |
| Title | Vvveb digital asset authorization bypass allows Vendors to list, read, edit, or delete other Vendors' digital assets | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-18T19:00:38.834Z
Reserved: 2026-05-28T03:42:34.341Z
Link: CVE-2026-49221
Updated: 2026-08-18T19:00:35.843Z
Status : Received
Published: 2026-08-18T16:17:13.357
Modified: 2026-08-18T20:17:15.650
Link: CVE-2026-49221
No data.
OpenCVE Enrichment
Updated: 2026-08-18T18:00:04Z