CVE-2018-15685: Electron webPreferences vulnerability can be used to perform remote code execution

electron Updated 02 Oct 2025

Summary

23/08/2018
Yes i
High
8.1

CVE-2018-15685: Electron webPreferences vulnerability can be used to perform remote code execution. Affects electron across 4 version ranges.

>= 1.7.0, < 1.7.16 >= 1.8.0, < 1.8.8 >= 2.0.0, < 2.0.8 >= 3.0.0-beta.1, < 3.0.0-beta.7

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Electron is an open-source framework that allows developers to build cross-platform desktop applications using web technologies such as HTML, CSS, and JavaScript. It provides a runtime environment for creating native-like applications for Windows, macOS, and Linux. Electron applications are built using a combination of Chromium and Node.js, which allows for the integration of web technologies with native desktop features. However, certain versions of Electron are affected by a webPreferences vulnerability that can be exploited to perform remote code execution.

Vulnerability Detail

The vulnerability in Electron versions 1.7.15, 1.8.7, 2.0.7, and 3.0.0-beta.6 arises in specific scenarios involving IFRAME elements and the 'nativeWindowOpen: true' or 'sandbox: true' options. This vulnerability can be leveraged by an attacker to execute arbitrary code remotely. The impact of this vulnerability can be severe, as it allows an attacker to gain control over the affected system and potentially perform malicious actions.

How To Fix

Latest published version: 45.0.0 as of 22 Oct 2026

npm install electron@45.0.0

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • >= 1.7.0, < 1.7.16 1.7.16
    npm install electron@1.7.16
  • >= 1.8.0, < 1.8.8 1.8.8
    npm install electron@1.8.8
  • >= 2.0.0, < 2.0.8 2.0.8
    npm install electron@2.0.8
  • >= 3.0.0-beta.1, < 3.0.0-beta.7 3.0.0-beta.7
    npm install electron@3.0.0-beta.7

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to the fixed versions of Electron.

Conclusion

The Electron webPreferences vulnerability can be exploited to perform remote code execution. It is crucial for developers to upgrade to the fixed versions of Electron to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for electron →

Share this vulnerability

FAQ

Electron is an open-source framework that allows developers to build cross-platform desktop applications using web technologies such as HTML, CSS, and JavaScript.

The vulnerability allows an attacker to perform remote code execution, potentially gaining control over the affected system and performing malicious actions.

To fix this vulnerability, it is recommended to upgrade Electron to version >=3.0.0-beta.7, >=2.0.8, >=1.8.8, or >=1.7.16.

There are no specific workarounds mentioned for this vulnerability. The recommended approach is to upgrade to the fixed versions of Electron.

More information about this vulnerability can be found on the Electron blog: https://electronjs.org/blog/web-preferences-fix

Related vulnerabilities

Recent vulnerabilities recorded for electron.

How To Fix

Latest published version: 45.0.0 as of 22 Oct 2026

npm install electron@45.0.0

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • >= 1.7.0, < 1.7.16 1.7.16
    npm install electron@1.7.16
  • >= 1.8.0, < 1.8.8 1.8.8
    npm install electron@1.8.8
  • >= 2.0.0, < 2.0.8 2.0.8
    npm install electron@2.0.8
  • >= 3.0.0-beta.1, < 3.0.0-beta.7 3.0.0-beta.7
    npm install electron@3.0.0-beta.7

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback