Cross-vendor revision access via product_id trust
Published Aug 18, 2026 · Updated Aug 18, 2026
Authorization bypass in Vvveb before 1.0.8.4 allows remote authenticated users to read or alter other Vendors' product revisions. The product/revisions controller reuses the generic revisions handler and accepts caller-supplied product_id, language_id, and created_at values, while the revision SQL reads, restores, and deletes records without binding those operations to the current Vendor's admin_id. Vendor-level access is required, after which an attacker can read historic product copy, restore stale revisions over another Vendor's live content, or delete revision records and audit history.
Summary
What happened
Authorization bypass in Vvveb before 1.0.8.4 allows remote authenticated users to read or alter other Vendors' product revisions. The product/revisions controller reuses the generic revisions handler and accepts caller-supplied product_id, language_id, and created_at values, while the revision SQL reads, restores, and deletes records without binding those operations to the current Vendor's admin_id. Vendor-level access is required, after which an attacker can read historic product copy, restore stale revisions over another Vendor's live content, or delete revision records and audit history.
The record
- CVE
- CVE-2026-49225
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- givanz
- Product
- Vvveb
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 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.4
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
- GHSA-gmrp-ccwf-xggq 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