DbGate: Unauthenticated Remote Code Execution via JSON Script Runner

published 2026-06-05 5 mo ago modified 2026-07-24 3 mo ago also GHSA-8v3q-9vmx-36vc , EUVD-2026-48340

cvss: 10.0; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 3.9%; EPSS 3.9% chance of exploitation in 30 days, percentile 90%
public exploits: 0; none known, plus a Nuclei check

DbGate is cross-platform database manager. In versions 7.1.8 and prior, DbGate's JSON script runner (`POST /runners/start`) allows remote code execution via code injection in the `functionName` parameter of JSON script `assign` commands. The `functionName` value is interpolated directly into dynamically generated JavaScript source code via string concatenation. The generated code is then executed in a forked Node.js child process. Version 7.1.9 contains a patch.

Patch / fix

fixed in 1 links 1

npm dbgate-serve 7.1.9

github.com/dbgate/dbgate/releases/tag/v7.1.9 release

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: total
Assessed: 3 mo ago (2026-07-23)

Exploit prediction

3.88% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

Nuclei template DbGate - Remote Code Execution via Anonymous JWT nuclei detection template
github.com https://github.com/dbgate/dbgate/security/advisories/GHSA-8v3q-9vmx-36vc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	10.0	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub	3.1	10.0	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	dbgate-serve	<7.1.9	7.1.9

Affected products

dbgate dbgate

Classification

Weakness

CWE-20 Improper Input Validation
CWE-94 Improper Control of Generation of Code
CWE-1188 Initialization of a Resource with an Insecure Default

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary