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.
Published: 2026-08-18
Score: 8.8 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Vvveb, a CMS for websites and e‑commerce, allows a low‑privileged vendor to view, list, edit, or delete digital assets belonging to other vendors because ownership checks on the digital_asset_id are missing. An attacker can therefore obtain private image or file metadata, change resource links, or cause irreversible data loss. The flaw is a classic instance of authorization bypass (CWE‑639) that directly compromises confidentiality, integrity, and availability of vendor‑owned content.

Affected Systems

The vulnerability affects all releases of the Vvveb CMS before version 1.0.8.4. The product is maintained by Givanz and is commonly deployed by individual vendors who publish their own digital assets. The fix is included in release 1.0.8.4 and later versions.

Risk and Exploitability

The CVSS score of 8.8 classifies the issue as high severity. EPSS information is not available, and the flaw has not yet been listed in the CISA KEV catalog, suggesting no mass exploitation has been observed. The likely attack vector is remote, performed by any authenticated vendor user via the CMS administrative interface. An attacker can exploit the uncontrolled digital_asset_id parameter to enumerate other vendors’ assets, read sensitive metadata, edit or delete records, and thereby compromise the integrity and availability of the affected assets. The absence of a containment boundary means the entire digital‑asset management service is at risk for a single vulnerable vendor account.

Generated by OpenCVE AI on August 18, 2026 at 17:50 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Vvveb CMS to version 1.0.8.4 or later, which addresses the missing ownership checks for digital assets.
  • If upgrading is temporarily infeasible, limit vendor access to the digital‑asset endpoints by applying access‑control rules or disabling the admin/controller/product/digital‑asset.php and admin/controller/product/digital‑assets.php routes for non‑admin vendors.
  • Verify that any custom plugins or extensions enforce vendor ownership validation before performing database operations on digital_asset_id fields to prevent similar authorization bypasses in the future.

Generated by OpenCVE AI on August 18, 2026 at 17:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 18 Aug 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


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

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-18T19:00:38.834Z

Reserved: 2026-05-28T03:42:34.341Z

Link: CVE-2026-49221

cve-icon Vulnrichment

Updated: 2026-08-18T19:00:35.843Z

cve-icon NVD

Status : Received

Published: 2026-08-18T16:17:13.357

Modified: 2026-08-18T20:17:15.650

Link: CVE-2026-49221

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T18:00:04Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key