Skip to main content

Vvveb CMS CVE-2026-45800

| EUVDEUVD-2026-30582 HIGH
SQL Injection (CWE-89)
2026-05-15 GitHub_M
8.7
CVSS 4.0 · Vendor: GitHub_M
View

Attack ChainAIDerived

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

  1. Access
    Obtain valid user credentials
  2. Delivery
    Log into Vvveb frontend
  3. Exploit
    Access /user/orders endpoint
  4. Execution
    Inject SQL via order_by parameter
  5. Impact
    Extract database contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Valid frontend user account credentials are required - the attacker must be able to authenticate and access the /user/orders endpoint. No special CMS configuration or non-default settings are needed beyond having user registration enabled. The vulnerability exists in default installations where authenticated users can view their order history. Anonymous users cannot exploit this issue.

Impact

The CVSS 4.0 score of 8.7 (High) reflects the serious impact potential, with the attack vector showing network accessibility (AV:N), low complexity (AC:L), and low privileges required (PR:L). The impact ratings are all High for confidentiality, integrity, and availability. However, the requirement for authenticated access significantly limits the attack surface compared to unauthenticated vulnerabilities. No EPSS score or KEV listing is available, and no public exploit code has been identified, suggesting this is not currently under active exploitation. The authentication requirement and lack of observed exploitation make this a lower priority than the CVSS score might suggest for external-facing deployments.

Exploit ScenarioDerived

An attacker with valid frontend user credentials logs into the Vvveb CMS and navigates to the order history page at /user/orders. By manipulating the order_by or direction URL parameters with SQL injection payloads, they can extract sensitive data from the database, modify records, or potentially execute system commands depending on database permissions.

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

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

Alert me

AnalysisAIv1 – May 15, 2026

SQL injection in Vvveb CMS versions before 1.0.8.3 allows authenticated frontend users to execute arbitrary SQL queries through the order history page. The vulnerability exists in the /user/orders endpoint where order_by and direction parameters are directly concatenated into SQL queries without sanitization, enabling database compromise with low-privileged user credentials. The vendor has released version 1.0.8.3 to address this issue.

RemediationAI

Upgrade to Vvveb CMS version 1.0.8.3 or later, which contains the vendor fix for this SQL injection vulnerability. The patch is available through the official Vvveb GitHub repository as documented in security advisory GHSA-vwcx-w4fq-9769. As an immediate workaround until patching is possible, consider restricting access to the /user/orders endpoint or implementing web application firewall rules to filter potentially malicious order_by and direction parameter values, though this may impact legitimate sorting functionality.

Affected VersionsENISA

Vvveb < 1.0.8.3

Affected Packages

euvd vvveb fix: 1.0.8.3

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

The vulnerability affects Vvveb CMS, an open-source content management system with page builder functionality. The issue stems from improper neutralization of special elements in SQL commands (CWE-89) where user-supplied input from URL parameters is directly concatenated into the ORDER BY clause in the OrderSQL::getAll() method. This classic SQL injection pattern occurs when dynamic query construction lacks parameterization or input validation, allowing attackers to modify the intended SQL logic.

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.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
May 15, 2026 - 20:02 EUVD
CVSS changed
May 15, 2026 - 19:22 NVD
8.7 (HIGH)

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.3, there is an authenticated SQL injection issue in the frontend user order history page in Vvveb CMS. A normal frontend user can log in and access /user/orders. The order_by and direction request parameters are accepted from the URL, propagated through the Orders component, and directly concatenated into the SQL ORDER BY clause in OrderSQL::getAll(). Because of this, attacker-controlled input reaches SQL structure without a whitelist or safe query construction step. This vulnerability is fixed in 1.0.8.3.

Executive ViewAI

Why It Matters

Vvveb CMS versions prior to 1.0.8.3 contain a SQL injection vulnerability in the order history functionality that allows authenticated users to execute arbitrary database queries, potentially compromising sensitive customer and business data stored in the CMS database. Organizations running affected versions face risk of data exfiltration and manipulation through legitimate user accounts.

Business Impact: High
Compensating Controls

Pending vendor patch availability confirmation: implement web application firewall (WAF) rules to block SQL injection patterns in order_by and direction parameters on /user/orders endpoint; restrict frontend user account creation and review existing user permissions to limit exposure surface; enable SQL query logging and establish alerts for anomalous database access patterns from application-level accounts; consider temporarily restricting order history page access if operationally feasible until patch deployment.

Threat Intelligence Overview

EPSS Score
0.0%
Top 99% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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.0%
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
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

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