dbcve.org
Nw.jsApplication · Nwjs

CVE-2014-9733

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-17
Fix available
A fix is available. Upgrade to after 0.11.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
nw.js before 0.11.5 can simulate user input events in a normal frame, which allows remote attackers to have unspecified impact via unknown vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

nw.js before 0.11.5 contains a vulnerability that allows the simulation of user input events within a normal (non-sandboxed) frame. This enables remote attackers to potentially execute arbitrary actions by mimicking legitimate user interactions such as clicks, form submissions, or keystrokes, leading to session hijacking, data manipulation, or unauthorized operations.

MitigationUpgrade nw.js to version 0.11.5 or later to address this vulnerability. Additionally, implement Content Security Policy (CSP) headers and ensure frames are properly sandboxed to limit the impact of simulated input events.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nw.jsApplication
Affected:<= 0.11.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed nw.js version
    Locate the nw.js binary or check the version field in your package.json file. Run 'nw --version' from the command line if nw.js is in your PATH, or inspect the nw.js executable's version info.
    Affected if The installed version is 0.11.4 or earlier (any version <= 0.11.4)
  2. Identify iframe and frame elements in your application
    Search your HTML files and dynamically loaded content for <iframe> and <frame> tags. Review any JavaScript code that creates frames programmatically using document.createElement('iframe') or similar methods.
    Affected if Any frame or iframe element exists without the 'sandbox' attribute or with sandbox permissions that allow scripts
  3. Verify sandbox attribute configuration
    For each identified frame, examine whether the sandbox attribute is present and what permissions it allows. A frame without sandbox or with permissions like 'allow-scripts allow-same-origin' is vulnerable.
    Affected if Frames lack the sandbox attribute or allow scripts without restricting same-origin access
  4. Check for Content Security Policy protection
    Inspect HTTP response headers for 'Content-Security-Policy' or look for <meta http-equiv='Content-Security-Policy'> tags in HTML pages. Determine if CSP rules are defined.
    Affected if No Content-Security-Policy header or meta tag is configured, or CSP does not include frame-src restrictions

Your environment is affected if you are running nw.js version 0.11.4 or earlier AND your application uses non-sandboxed frames without CSP protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.11.4
Interim mitigation

Upgrade nw.js to version 0.11.5 or later to address this vulnerability. Additionally, implement Content Security Policy (CSP) headers and ensure frames are properly sandboxed to limit the impact of simulated input events.

Recommended fix Moderate confidence

nw.js 0.11.5

  1. Upgrade nw.js to version 0.11.5 or later to remediate this vulnerability
  2. Verify the upgrade by checking the nw.js version using process.versions.nw or the --version command line flag
  3. Test that the application functions correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nw.js Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-9733 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data