CVE-2026-45800
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVvveb 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAuthenticated SQL injection vulnerability in Vvveb CMS allows frontend users to inject malicious SQL via the order_by and direction parameters on the /user/orders page. These parameters are directly concatenated into the ORDER BY clause in OrderSQL::getAll() without sanitization or parameterized query construction, enabling attackers with standard user accounts to manipulate database queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Vvveb CMS installationIdentify if Vvveb CMS is running in your environment by checking for Vvveb-specific files, headers, or the presence of the application web root.Affected if Vvveb CMS is not installed - the CVE does not apply.
-
Check Vvveb CMS versionLocate the version file or admin panel 'About' section to determine the installed Vvveb CMS version number.Affected if Version is below 1.0.8.3 - the vulnerable version is present.
-
Verify user registration is enabledCheck if frontend user registration or account creation is enabled in the CMS settings, as the attacker needs a standard user account to exploit this flaw.Affected if User accounts can be created or existing user accounts exist - the exploitation prerequisite is met.
-
Locate vulnerable OrderSQL classSearch the codebase for the OrderSQL class file containing the getAll() method and inspect the ORDER BY clause implementation for order_by and direction parameters.Affected if The code directly concatenates order_by/direction parameters into the ORDER BY clause without sanitization or prepared statements.
-
Test parameter handling on /user/ordersWith a standard user account, access the /user/orders page and inspect how the order_by and direction parameters are handled in the HTTP request/response.Affected if The application accepts and processes arbitrary values in these parameters without validation.
A user is affected if they have Vvveb CMS version below 1.0.8.3 with user accounts enabled and the vulnerable OrderSQL::getAll() code present without input validation on order_by/direction parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Vvveb CMS version 1.0.8.3 or later which contains the fix. As a temporary workaround, implement whitelist validation for order_by and direction parameters to restrict input to known-good column names and sort directions before the fix is applied.
Vvveb CMS 1.0.8.3
- 1. Backup your current Vvveb CMS installation and database before making any changes.
- 2. Download Vvveb CMS version 1.0.8.3 from the official GitHub repository or release channel.
- 3. Upgrade your existing Vvveb installation to version 1.0.8.3 following the standard upgrade procedure.
- 4. Verify the upgrade was successful by logging in as a frontend user.
- 5. Navigate to /user/orders and test that the order_by and direction parameters function correctly with legitimate values.
- 6. Confirm the SQL injection vulnerability is remediated by verifying the fix in OrderSQL::getAll() uses safe query construction.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45800 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data