dbcve.org
WebstormApplication · Jetbrains

CVE-2024-52555

HIGH · 7.8 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 2024.3.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
In JetBrains WebStorm before 2024.3 code execution in Untrusted Project mode was possible via type definitions installer script

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 · high confidence

JetBrains WebStorm before version 2024.3 contains a vulnerability in Untrusted Project mode that allows arbitrary code execution through the type definitions installer script. An attacker could exploit this by crafting malicious type definition packages that execute code during the installation process in untrusted project contexts.

MitigationUpgrade WebStorm to version 2024.3 or later to obtain the patch. Avoid opening untrusted projects in the IDE until the update is applied.

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
WebstormApplication
Affected:< 2024.3.0

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 WebStorm version
    Open WebStorm, go to Help > About, or check the application bundle version. On Windows check Help > About WebStorm. On macOS check WebStorm > About WebStorm from the menu bar.
    Affected if The version shown is earlier than 2024.3.0 (e.g., 2024.2.x, 2024.1.x, or any version below 2024.3.0)
  2. Verify Untrusted Project mode status
    When opening a project, WebStorm may prompt about trusting the project. Check if you have opened any projects in 'Trust' or 'Open as Untrusted' mode. Look for the security indicator in the IDE status bar - untrusted projects typically show an open folder icon with a warning or restricted badge.
    Affected if Untrusted Project mode is active, indicated by restricted execution settings or project trust warnings in the IDE
  3. Identify recent type definition installations
    Review recent npm/yarn install activity, particularly @types/* package installations. Check package.json files for @types dependencies installed recently, or review IDE logs for type definition download events.
    Affected if Any @types packages or type definition packages have been installed recently in an untrusted project context
  4. Check IDE security settings
    Go to Settings > Security in WebStorm and examine the Trust settings. Look for the 'Project' or 'Trust' section to see how project trust is configured.
    Affected if Projects are set to be opened as untrusted, or trust decisions have been made to allow execution in untrusted contexts

You are affected if WebStorm version is below 2024.3.0 AND you use Untrusted Project mode with type definition installations.

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 2024.3.0 or later
Fixed in 2024.3.0
Interim mitigation

Upgrade WebStorm to version 2024.3 or later to obtain the patch. Avoid opening untrusted projects in the IDE until the update is applied.

Recommended fix High confidence

WebStorm 2024.3.0 or later

  1. Back up any custom WebStorm settings and configurations if desired
  2. Open WebStorm and navigate to Help > Check for Updates (or Settings > Appearance & Behavior > System Settings > Updates)
  3. Follow the prompts to update to version 2024.3.0 or later
  4. Alternatively, download the latest version directly from jetbrains.com/webstorm/download
  5. Restart WebStorm after the update completes
  6. Verify the update was successful by checking Help > About WebStorm shows version 2024.3.0 or higher
Caveat IDE upgrades typically have minimal impact on project code; however, verify plugin compatibility with the new version

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

Fix this in Webstorm Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing0.5 h
  • Review / QA0.5 h
2.5 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52555 — 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-2024-52555 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