/

CVE-2026-49223

Severity:

HIGH RISK

(7.6)

Authorization Bypass (CWE-639) in Vvveb Product Reviews

CVE-2026-49223

Deferred

Vulnerability type

Category:

Broken Object-Level Authorization

CWE:

CWE-639

Impact:

Unauthorized access and modification of product reviews

Severity:

HIGH RISK

(7.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A broken object-level authorization flaw in Vvveb allows a low-privileged Vendor to access and manage product reviews belonging to another Vendor.

If an attacker can submit or obtain another product review identifier, they may read review details, alter moderation state or content, and delete reviews without proper ownership verification.

Affected context

This issue occurs in Vvveb backend product review operations when review-management queries accept a caller-controlled product_review_id without confirming that the associated product belongs to the currently authorized Vendor. Deployments are at risk when low-privileged Vendor accounts can reach these operations and object ownership is not enforced consistently across read, update, status-change, and delete actions.

Exploit preconditions

  • Attack surface: Vvveb backend product review management endpoints
  • Required access: A valid low-privileged Vendor account
  • Trigger point: An operation that accepts a product review identifier
  • Why exploitation is possible: Authorization checks do not reliably bind the selected review's product to the current Vendor's administrative scope

Why this happens

The underlying bug is an object-level authorization failure. Backend queries trust a caller-controlled product_review_id but do not verify that the referenced review is associated with a product owned by the current administrator or Vendor.

This maps to CWE-639: Authorization Bypass Through User-Controlled Key, where an attacker can substitute an object identifier and access or manipulate records outside the intended authorization boundary.

Potential impact

  • Unauthorized disclosure of pending review content, ratings, author information, and moderation state
  • Unauthorized changes to review content or moderation status
  • Deletion of reviews belonging to another Vendor
  • Manipulation of product review visibility and integrity
  • Reputational or business impact for affected Vendors

General mitigation guidance

Mitigation typically focuses on enforcing object-level authorization at every product review operation.

Common defensive patterns include:

  • Deriving ownership scope from the authenticated session rather than trusting client-supplied identifiers
  • Applying authorization predicates that bind each review to an authorized product and Vendor
  • Enforcing the same ownership checks for reads, updates, status changes, and deletes
  • Centralizing authorization logic to prevent inconsistent checks across queries
  • Returning indistinguishable responses for unauthorized and nonexistent objects where appropriate
  • Applying least privilege to Vendor roles and limiting access to moderation functions

How teams detect issues like this

Organizations commonly detect this class of issue through:

  • Static analysis and code review for queries that use user-controlled object identifiers without ownership predicates
  • Tests that attempt cross-account access to read, update, and delete operations
  • Review of authorization middleware and database filters for tenant or Vendor scoping
  • Policy checks requiring every object-level operation to validate the authenticated principal's relationship to the target record
  • Audit logging and alerting for unusual cross-Vendor review access or bulk moderation changes

Automated security testing and code review tools can help identify missing authorization checks, but should be complemented by multi-tenant access-control tests.

Sources

SourceLink
github.comgithub.com/givanz/Vvveb/commit/3d5c15dcf4b50e4580161f05cb9e643d834d044a
github.comgithub.com/givanz/Vvveb/releases/tag/1.0.8.4
github.comgithub.com/givanz/Vvveb/security/advisories/GHSA-cj37-c5m2-3jmc

Frequently asked

questions

It may be exploitable through accessible Vvveb backend operations if a low-privileged Vendor can authenticate and submit a review identifier for an object outside their ownership scope.

The described issue requires a valid low-privileged Vendor account and access to the affected product review management functionality. Anonymous access is not implied.

Enforce server-side object-level authorization on every operation, verifying that the target review belongs to a product within the authenticated Vendor's authorized scope.

Use centralized authorization policies, scope database queries by the authenticated principal, and include cross-tenant read, update, and delete tests in development and security validation workflows.

Find out what's already
exploitable in your codebase.