Skip to main content

Vvveb CMS CVE-2026-49224

| EUVDEUVD-2026-61038 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-08-18 GitHub_M
8.3
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege Author
  2. Delivery
    Enumerate post_id values via revision list endpoint
  3. Exploit
    Read victim author's draft or unpublished revision content
  4. Execution
    Optionally restore chosen revision over victim's live post
  5. Impact
    Delete revision records to erase audit trail

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires a valid Author-level (or equivalent low-privilege) authenticated account on the target Vvveb CMS installation. The CVSS vector PR:L confirms this authentication prerequisite. The vulnerable condition exists in default multi-author deployments - no non-default configuration is required beyond having more than one author account registered. Exploitation is limited to the revision management feature and requires knowledge of or ability to enumerate target post_id values, which are typically sequential integers. There is no user interaction required from the victim. Single-author deployments have no practical exposure from this vulnerability since there are no other authors' revisions to access.

Impact

The CVSS 8.3 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L) is well-calibrated for this vulnerability. Attack complexity is genuinely low - any Author account is sufficient, no additional configuration is required, and the exploit is as simple as substituting a different post_id in a revision API request. The integrity impact rated H is the most consequential aspect: an attacker can silently restore a stale or adversary-crafted revision over another author's currently-published post, corrupting live content without triggering any obvious alert. The confidentiality impact rated H covers exposure of unpublished drafts and historical revisions that authors may reasonably expect to be private. The availability impact rated L reflects revision record deletion, which removes audit history but does not destroy the live post itself. The vulnerability is not listed in CISA KEV, no EPSS data was provided, and no public exploit code has been identified - these signals suggest exploitation risk is currently theoretical rather than actively observed, though the low complexity and published advisory lower the bar significantly for any attacker with a valid Author credential. The CVSS Scope:Unchanged rating is appropriate - the attacker remains within the CMS application boundary throughout.

Exploit ScenarioDerived

An attacker with a low-privileged Author account on a multi-author Vvveb site enumerates integer post_id values by iterating revision list requests against the revisions controller, retrieving draft content from posts they do not own. The attacker then selects a target post, calls the restore operation with a chosen revision_id and the victim's post_id, and silently overwrites the live published post with older or attacker-selected content - with no notification to the post's legitimate owner.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 18, 2026

Post revision operations in Vvveb CMS prior to 1.0.8.4 expose an Insecure Direct Object Reference that allows any authenticated Author-role user to read, restore, or delete revision records belonging to other authors. The affected controller passes caller-supplied post_id, language_id, and created_at values directly to SQL queries without enforcing admin_id ownership, enabling cross-author access across list, read, restore, and delete operations. No public exploit code has been identified at time of analysis, and a vendor-released patch is available in version 1.0.8.4.

RemediationAI

Upgrade to Vvveb CMS version 1.0.8.4, which is the vendor-released patch addressing this issue. The fix is available at https://github.com/givanz/Vvveb/releases/tag/1.0.8.4 and the corrective commit is cbedd3754bccf8b7584f02ab301291f12e888b7e. If immediate upgrade is not possible, restrict Author-role account creation to fully trusted users only, as any Author account can be weaponized. As a compensating control, administrators can temporarily disable or firewall access to the revision management endpoints in admin/controller/content/revisions.php - this removes revision functionality for all users but eliminates the attack surface. Review existing Author accounts for suspicious activity including unexpected revision restores or deletions in the audit log, as exploitation leaves no special footprint beyond normal revision operations.

Affected VersionsENISA

Vvveb < 1.0.8.4

Affected Packages

euvd vvveb fix: 1.0.8.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Vvveb is a PHP-based CMS and page builder (CPE: cpe:2.3:a:givanz:vvveb:*:*:*:*:*:*:*:*) supporting SQLite, MySQL, and PostgreSQL backends. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key): the controller admin/controller/content/revisions.php accepted caller-controlled object identifiers and routed them to SQL procedures in post_content_revision.sql without consistently appending an admin_id ownership predicate. All four revision operations - getAll (list), get (read), edit/save (restore), and delete - were affected. The fix in commit cbedd3754bccf8b7584f02ab301291f12e888b7e introduces Admin::hasCapability() checks for view_other_posts, edit_other_posts, view_other_products, and edit_other_products, and adds conditional WHERE admin_id = :admin_id clauses to all four SQL procedures across all three database backends. Without the elevated capability, the current admin_id is now enforced server-side.

Know when Vvveb gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.3 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
vuln.today AI 8.3 HIGH

Network-accessible IDOR requiring only Author credentials (PR:L); no complexity barriers; integrity and confidentiality fully compromised; availability limited to revision record loss.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

Lifecycle Timeline

2
Patch available
Aug 18, 2026 - 17:17 EUVD
CVE Published
Aug 18, 2026 - 16:17 cve.org
HIGH 8.3

DescriptionCVE.org

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 post revision operations allow a low-privileged Author to access revisions for posts owned by another Author. The admin/controller/content/revisions.php controller and admin/sql/sqlite/post_content_revision.sql queries trust caller-controlled post_id, language_id, and created_at values without consistently applying the current admin_id to revision lists, reads, restores, and deletes. An attacker can read historic post content, restore a revision over another Author's live post content, or delete revision records, exposing drafts, corrupting published content, and removing audit history. This issue is fixed in version 1.0.8.4.

Executive ViewAI

Why It Matters

Vvveb CMS versions prior to 1.0.8.4 contain an IDOR vulnerability in post revision operations that allows authenticated Author-role users to read, restore, and delete revision records belonging to other authors, compromising editorial control and audit trail integrity. This directly impacts content governance and creates compliance risk for organizations managing multi-author workflows.

Business Impact: High
Compensating Controls

Apply vendor patch to version 1.0.8.4.

Threat Intelligence Overview

EPSS Score
0.4%
Top 64% exploitable
Prevalence
Low
niche PHP CMS with limited enterprise adoption
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Vvveb

View all
CVE-2025-44022 CRITICAL POC
9.8 May 12

An issue in vvveb CMS v.1.0.6 allows a remote attacker to execute arbitrary code via the Plugin mechanism. Rated critica

CVE-2025-8518 LOW POC
2.0 Aug 04

A vulnerability was found in givanz Vvveb 1.0.5. Rated medium severity (CVSS 5.1), this vulnerability is remotely exploi

CVE-2024-29272 MEDIUM POC
6.5 Mar 22

Arbitrary File Upload vulnerability in VvvebJs before version 1.7.5, allows unauthenticated remote attackers to execute

CVE-2024-29271 MEDIUM POC
6.1 Mar 22

Reflected Cross-Site Scripting (XSS) vulnerability in VvvebJs before version 1.7.7, allows remote attackers to execute a

CVE-2025-11028 MEDIUM POC
5.5 Sep 26

A security flaw has been discovered in givanz Vvveb up to 1.0.7.2. Rated medium severity (CVSS 5.5), this vulnerability

CVE-2025-9728 MEDIUM POC
5.3 Aug 31

A security vulnerability has been detected in givanz Vvveb 1.0.7.2. Rated medium severity (CVSS 5.3), this vulnerability

CVE-2026-6257 CRITICAL
9.2 Apr 20

Remote code execution in Vvveb CMS v1.0.8 allows authenticated administrators to execute arbitrary system commands as ww

CVE-2026-39918 CRITICAL
9.2 Apr 20

Remote code execution in Vvveb CMS versions prior to 1.0.8.1 allows unauthenticated attackers to inject arbitrary PHP co

CVE-2026-41930 CRITICAL
9.2 May 06

Hard-coded credentials in Vvveb's Docker deployment expose the entire application database to unauthenticated remote att

CVE-2026-34429 MEDIUM POC
5.1 Apr 20

Stored cross-site scripting in Vvveb prior to 1.0.8.1 allows authenticated users with media upload and rename permission

CVE-2026-49228 HIGH
8.8 Aug 18

Insecure Direct Object Reference in Vvveb CMS prior to 1.0.8.4 allows any authenticated low-privileged Vendor to read, d

CVE-2026-49221 HIGH
8.8 Aug 18

Broken object-level authorization in Vvveb CMS prior to 1.0.8.4 allows an authenticated low-privilege Vendor to access,

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy