CVE-2026-47668: DbGate: Unauthenticated Remote Code Execution via JSON Script Runner
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.
Security readout for executives and security teams
Plain-English summary
DbGate versions before 7.1.9 can let an unauthenticated network attacker make the server execute arbitrary code. Successful compromise could expose databases and credentials, alter information, disrupt service, and potentially affect connected systems. Risk is greatest where the DbGate service or vulnerable runner endpoint is reachable from untrusted networks.
Executive priority
Treat this as an emergency patching issue for reachable deployments. Upgrade externally exposed instances immediately, then remediate internal instances based on accessibility and data sensitivity. If rapid upgrading is impossible, isolate access and increase monitoring. Absence from KEV should not reduce urgency because exploitation requires no authentication and can fully compromise the service environment.
Technical view
The JSON script runner at POST /runners/start insufficiently validates functionName in assign commands. DbGate concatenates that value into generated JavaScript, then executes the code in a forked Node.js child process. The CVSS 3.1 score is 10.0, reflecting network access, low complexity, no authentication or user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
DbGate installations running 7.1.8 or earlier are affected. Practical exposure depends on whether attackers can reach the DbGate service and POST /runners/start. Internet-facing deployments, broadly accessible internal services, and environments where DbGate can reach sensitive databases or credentials warrant immediate attention. The bundle provides no CPE-based inventory identifiers.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation. A public Nuclei template exists, indicating that detection knowledge is publicly available. This increases discovery pressure but does not establish compromise or exploitation in the wild.
Researcher notes
The vulnerability is a source-generation injection flaw: attacker-controlled functionName data crosses into executable JavaScript through string concatenation. Execution occurs in a forked Node.js process, creating a direct path from the unauthenticated runner request to code execution. The record associates CWE-1188, CWE-20, and CWE-94. The supplied evidence does not describe sandboxing, default exposure, logging behavior, or observed attacks.
Mitigation direction
Upgrade DbGate to version 7.1.9 or later.
Prioritize internet-facing and broadly accessible DbGate installations.
Restrict DbGate access to trusted administrators and networks until upgraded.
Check the vendor advisory and release notes for deployment-specific guidance.
Protect database and service credentials accessible from affected hosts.
Validation and detection
Inventory DbGate installations and record their exact versions.
Confirm no production instance remains below version 7.1.9.
Determine whether untrusted networks can reach POST /runners/start.
Verify temporary access restrictions are enforced from untrusted network segments.
Review DbGate and host telemetry for unexpected runner activity or child processes.
Confirm the upgraded service operates normally and retains required access controls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1188: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.