CVE
Vvveb remote code execution in code editor via .sql file save
Affects Vvveb 1.0.8.6 and earlier when a restricted site_admin account can reach the admin code editor, with SQL_CHECK enabled, its default. The checked facts name no fixed version or patch.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Vvveb version 1.0.8.6 or earlier Attacker holds a restricted site_admin role (non-super-admin) with access to the admin code editor SQL_CHECK enabled, which is the default setting
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.83% · 58th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vvveb through 1.0.8.6 contains a remote code execution vulnerability allowing restricted site_admin roles to inject PHP by saving .sql files through the admin code editor. Attackers can bypass extension and content deny-lists with an @IF macro payload that compiles into executable PHP when the model loads, running OS commands as the web user.
Who should check
Teams running givanz Vvveb 1.0.8.6 or earlier that give site_admin or other non-super-admin roles access to the admin code editor
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 29 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Vvveb version 1.0.8.6 or earlier Attacker holds a restricted site_admin role (non-super-admin) with access to the admin code editor SQL_CHECK enabled, which is the default settingWorkaround: The checked facts include no vendor workaround. Limiting which accounts hold the site_admin role and which can reach the admin code editor narrows exposure to this flaw.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126370 (Vvveb through 1.0.8.6 Authenticated RCE via .sql Code Injection in editor/code/save), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126370 (entry last updated 2026-11-13):
Affected:
- givanz Vvveb: through 1.0.8.6
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Vvveb version 1.0.8.6 or earlier (source: https://www.vulncheck.com/advisories/vvveb-through-1.0.8.6-authenticated-rce-via-sql-code-injection-in-editor-code-save)
- Attacker holds a restricted site_admin role (non-super-admin) with access to the admin code editor (source: https://github.com/givanz/Vvveb/security/advisories/GHSA-2mq4-4q7r-q52q)
- SQL_CHECK enabled, which is the default setting (source: https://github.com/givanz/Vvveb/security/advisories/GHSA-2mq4-4q7r-q52q)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126370 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126370 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/givanz/Vvveb/security/advisories/GHSA-2mq4-4q7r-q52q
- https://www.vulncheck.com/advisories/vvveb-through-1.0.8.6-authenticated-rce-via-sql-code-injection-in-editor-code-save
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126370
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126370"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- givanz Vvveb
through 1.0.8.6
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126370
Is CVE-2026-126370 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A restricted site_admin account can inject code through the .sql save path in the admin code editor (editor/code/save). This allows arbitrary PHP and OS command execution as the web user, which can extend the account's reach to the full host and co-hosted sites.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126370?
Vvveb: through 1.0.8.6.Source: cve.now feed data
Am I affected, and how do I check?
Vvveb version 1.0.8.6 and earlier, where SQL_CHECK is enabled. SQL_CHECK defaults to true in env.php at line 25, so check that setting there, and check your installed version in the project files.Source: vulncheck.com, github.com
How do I fix CVE-2026-126370?
The checked facts name no fixed version and no vendor patch, so no upgrade target can be given from them. Check the project's advisory or release notes for a fix before relying on any update.Source: vulncheck.com, github.com
What if there's no patch?
The checked facts include no vendor workaround. Limiting which accounts hold the site_admin role and which can reach the admin code editor narrows exposure to this flaw.Source: vulncheck.com, github.com