CVE-2023-23623
Electronjs Electron 22.0.0 … 23.0.0
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-23623 is a high-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Electronjs Electron. Its CVSS base score is 7.5 (High).
Operationally, ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-2513
Vulnerability Data
Electron is a framework which lets you write cross-platform desktop applications using JavaScript, HTML and CSS. A Content-Security-Policy that disables eval, specifically setting a `script-src` directive and _not_ providing `unsafe-eval` in that directive, is not respected in renderers that have…
more
sandbox disabled. i.e. `sandbox: false` in the `webPreferences` object. This allows usage of methods like `eval()` and `new Function` unexpectedly which can result in an expanded attack surface. This issue only ever affected the 22 and 23 major versions of Electron and has been fixed in the latest versions of those release lines. Specifically, these versions contain the fixes: 22.0.1 and 23.0.0-alpha.2 We recommend all apps upgrade to the latest stable version of Electron. If upgrading isn't possible, this issue can be addressed without upgrading by enabling `sandbox: true` on all renderers.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.25 mandates an SDLC process that includes security requirements, checkpoints, secure coding guidelines, testing and developer training, which reaches a slice of control-flow defects but leaves most implementation bugs untouched without perfect enforcement at every checkpoint.
Secure coding standards and reviews directly target flawed control-flow implementations.
Security testing in development and acceptance can detect paths that deviate from intended logic.
A.8.32 mandates a formal process for planning, authorizing, testing and documenting changes but does not itself inspect, correct or block the incorrect control-flow logic that CWE-670 describes; the defect can still be introduced and exploited if the developer writes it and the process accepts it.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-670, a class-level weakness, and none of its children carries one either.