Vvveb product question authorization bypass allows Vendors to read, approve, edit, or delete questions under other Vendors' products (givanz Vvveb)

CVE-2026-49222
HIGH 7.6

At a glance

Source
NVD
EPSS
EPSS 0.42 % · percentile 36 ()
State
PUBLISHED
Published
Updated
Assigner
GitHub_M
NVD status
Deferred

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 product question operations allow a low-privileged Vendor to manage questions under another Vendor's products. The admin/sql/sqlite/product_question.sql queries accept a caller-controlled product_question_id and do not verify product_question.product_id against product.admin_id for the current admin_id. An attacker can read pending question content and moderation data, change question status, edit question content, or delete questions, manipulating product Q&A visibility and integrity. This issue is fixed in version 1.0.8.4.

Weaknesses (CWE)

  • CWE-639 — Authorization Bypass Through User-Controlled Key

References

Scores

VersionScoreVectorScored by
CVSS 3.1HIGH 7.6CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:LGitHub_M
CVSS 3.1HIGH 7.6CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:LNVD · security-advisories@github.com (Secondary)

European references

Affected products

ProductVersions
givanz · Vvvebaffected < 1.0.8.4

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD