Quick answers
- Is CVE-2026-123992 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123992 being exploited in the wild.
- How severe is CVE-2026-123992?
- Medium severity, with a CVSS score of 4.3, published 7 November 2026.
- Which products and versions are affected?
- DataEase up to 2.10.27.
- Is there a fix for CVE-2026-123992?
- Yes: fixed in 2.10.28. Until then: Upgrade to DataEase 2.10.28 or later. Restrict upload and access to SVG files if upgrading is not immediately possible. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123992 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123992?
- Check whether you run DataEase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.10.28
Upgrade to DataEase 2.10.28 or later. Restrict upload and access to SVG files if upgrading is not immediately possible.
Technical details
A cross-site scripting (XSS) vulnerability exists in the StaticResourceServer.validateSvgContent function due to insufficient validation of SVG content, allowing attackers to bypass security checks through tab/entity-based URL manipulation. The vulnerability affects the SVG Handler component in DataEase and can be exploited remotely without authentication. The fix replaces blacklist-based validation with namespace-aware allowlists, restricts references to document-local fragments, and applies restrictive Content Security Policy headers.
Affected products
- DataEase DataEase up to 2.10.27
Timeline
- 2026-11-07: disclosed
- 2026-11-07: patched: Patch 0709fe98d6608c3507daee3e92cf433e7ff61370 released