Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

dbgate-web: Stored XSS in applicationIcon leads to potential RCE in Electron due to unsafe renderer configuration

CVE-2026-34725GHSA-35xm-qvjg-8m42

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (dbgate-web 7.1.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm dbgate-web

    Affected
    >= 7.0.0, < 7.1.5
    Fixed in
    7.1.5

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.2 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-34725: 0.18% estimated exploitation activity in the next 30 days; percentile 6.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A stored XSS vulnerability exists in DbGate because attacker-controlled SVG icon strings are rendered as raw HTML without sanitization. In the web UI this allows script execution in another user's browser; in the Electron desktop app this can escalate to local code execution because Electron is configured with nodeIntegration: true and contextIsolation: false. Details The issue is in the icon rendering path: - packages/web/src/icons/FontIcon.svelte - treats any icon string starting with <svg as inline SVG - renders it with {@html iconValue} without sanitization - packages/api/src/controllers/apps.js - loads app definitions from disk and returns applicationIcon to clients unchanged - packages/web/src/appobj/DatabaseAppObject.svelte - passes applicationIcon into additionalIcons - packages/web/src/appobj/AppObjectCore.svelte - renders those icons through <FontIcon icon={ic.icon} This makes applicationIcon a stored XSS sink. An attacker who can create or modify an app definition…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-35xm-qvjg-8m42

  2. Revision 1 · created ·

    Published from osv record GHSA-35xm-qvjg-8m42

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34725

Advisory: dbgate-web: Stored XSS in applicationIcon leads to potential RCE in Electron due to unsafe renderer configuration
IDs: CVE-2026-34725, GHSA-35xm-qvjg-8m42
Record: https://patchnext.com/advisories/cve-2026-34725 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dbgate-web 7.1.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm dbgate-web: affected >= 7.0.0, < 7.1.5; fixed in 7.1.5

## Suggested inspection (read-only)
- `npm ls dbgate-web --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dbgate-web.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-35xm-qvjg-8m42 (OSV record GHSA-35xm-qvjg-8m42 lists affected ranges: npm dbgate-web >=7.0.0 <7.1.5 (fixed))
- Verified: https://github.com/advisories/GHSA-35xm-qvjg-8m42 (GitHub-reviewed advisory GHSA-35xm-qvjg-8m42 lists affected ranges: npm dbgate-web >=7.0.0 <7.1.5)

Commands are suggestions: review each one before running it.

Loading voting…