dbcve.org
Plotly.jsApplication · Plotly

CVE-2023-46308

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-03
Fix available
A fix is available. Upgrade to 2.25.2 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
In Plotly plotly.js before 2.25.2, plot API calls have a risk of __proto__ being polluted in expandObjectPaths or nestedProperty.

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

This is a __proto__ prototype pollution vulnerability in plotly.js versions before 2.25.2. The expandObjectPaths and nestedProperty functions within the plot API do not properly sanitize user-supplied input, allowing attackers to inject properties into Object.prototype by manipulating the __proto__ attribute. This can lead to denial of service, application behavior manipulation, or potentially remote code execution depending on how the application uses the polluted objects.

MitigationUpgrade plotly.js to version 2.25.2 or later which contains the fix for this prototype pollution vulnerability. Additionally, implement input validation on all API endpoints that accept user data before passing to plot functions.

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
Plotly.jsApplication
Affected:< 2.25.2

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.1/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. Identify plotly.js version in use
    Locate the plotly.js library in your application (check package.json, node_modules, CDN references, or bundled files) and identify the version number. Common methods: check package.json dependencies, inspect the plotly.min.js file header, or run 'npm list plotly.js' if using npm
    Affected if The installed version is lower than 2.25.2
  2. Determine if expandObjectPaths is called with user data
    Search your codebase for calls to 'expandObjectPaths' function from plotly.js. Review whether any user-controlled input (request parameters, API payloads, user files) is passed as the argument to this function
    Affected if User-supplied data flows directly to expandObjectPaths without sanitization and your plotly.js version is below 2.25.2
  3. Determine if nestedProperty is called with user data
    Search your codebase for calls to 'nestedProperty' function from plotly.js. Review whether any user-controlled input is passed as the object path or property name argument to this function
    Affected if User-supplied data flows directly to nestedProperty without sanitization and your plotly.js version is below 2.25.2
  4. Inspect API endpoints passing data to plotly functions
    Review all API endpoints or data ingestion points that feed user data into plotly.js rendering functions. Check if __proto__ or constructor attributes in the data are being passed through to plotly's internal property manipulation functions
    Affected if User data containing __proto__ attributes reaches plotly.js internal functions and your version is below 2.25.2

You are affected if your environment runs any plotly.js version below 2.25.2 AND passes user-supplied input to expandObjectPaths, nestedProperty, or similar plotly property-setting functions without filtering __proto__ or constructor attributes.

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

Upgrade plotly.js to version 2.25.2 or later which contains the fix for this prototype pollution vulnerability. Additionally, implement input validation on all API endpoints that accept user data before passing to plot functions.

Recommended fix High confidence

2.25.2

  1. Check the current version of plotly.js installed in your project by running `npm list plotly.js` or checking your package.json
  2. Update your package.json to specify plotly.js version 2.25.2 or later: change `"plotly.js": "^<current_version>"` to `"plotly.js": "^2.25.2"`
  3. Run `npm install` or `npm update plotly.js` to install the fixed version
  4. Verify the installation was successful by running `npm list plotly.js` and confirming the version is 2.25.2 or higher
  5. Test your application to ensure the upgrade does not break existing functionality

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

Fix this in Plotly.js Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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