# CVE-2026-45800: Vvveb: Authenticated SQL injection in /user/orders via order_by and direction

> Authenticated users can execute arbitrary SQL commands via the order history page, potentially exposing or modifying data.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2026
- **Updated:** 16 May 2026
- **Also known as:** GHSA-vwcx-w4fq-9769

## What is CVE-2026-45800?

CVE-2026-45800 is a high-severity SQL injection vulnerability in givanz Vvveb, published on 15 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-45800?


## How do I fix CVE-2026-45800?

No fix has been published for CVE-2026-45800 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45800 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45800 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45800 and fix it if it is affected.

What it is: CVE-2026-45800 is a high-severity SQL injection vulnerability in givanz Vvveb, published on 15 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45800 exists.

Affected product: givanz Vvveb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45800/ (Markdown: https://insights.sbomify.com/CVE-2026-45800/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45800
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45800
- OSV: https://osv.dev/vulnerability/CVE-2026-45800

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45800/
Summaries are generated and may contain mistakes; the official description above is the record.