Skip to main content
VulnerabilityPublished

CVE-2026-45800: givanz Vvveb · SQL Injection

Affects givanz VvvebSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 1.0.8.3 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.8.3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Vvveb and givanz/Vvveb to 1.0.8.3.

Affected software

ProductAffectedFixed in
givanzVvvebAffected
  • <1.0.8.3
Fixed in
  • 1.0.8.3
GitHubgivanz/Vvvebpkg:github/givanz/VvvebOther threatsAffected
  • <1.0.8.3
Fixed in
  • 1.0.8.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vvveb CMS to version 1.0.8.3 or later, where this SQL injection vulnerability is fixed. Until upgraded, restrict access to the affected functionality or implement strict input validation and parameter whitelisting on 'order_by' and 'direction' parameters if possible.

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.

References

Community reviews

Loading reviews…