Skip to main content
VulnerabilityPublished Updated

CVE-2023-46308: Plotly plotly.js · Prototype Pollution

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.25.2 as a priority.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.25.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade plotly.js to 2.25.2.

Affected software

ProductAffectedFixed in
npmplotly.jspkg:npm/plotly.jsOther threatsAffected
  • <2.25.2
Fixed in
  • 2.25.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade all instances of plotly.js to version 2.25.2 or later immediately, as this version addresses the prototype pollution vulnerability.
  2. Conduct a thorough audit of all web applications and services using plotly.js to identify and isolate vulnerable versions.
  3. Review and sanitize any custom code that manipulates object properties or paths to prevent prototype pollution vectors.
  4. Implement runtime application self-protection (RASP) or web application firewalls (WAF) with rules targeting prototype pollution attack patterns.
  5. Monitor logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected object property modifications or anomalous API calls.
  6. Educate development teams on secure coding practices related to JavaScript object handling to prevent similar vulnerabilities.
  7. Coordinate with third-party vendors and SaaS providers to confirm they have patched this vulnerability if their products incorporate plotly.js.
  8. Establish incident response plans specifically addressing prototype pollution exploitation scenarios to enable rapid containment and recovery.

Description

In Plotly plotly.js before 2.25.2, plot API calls have a risk of __proto__ being polluted in expandObjectPaths or nestedProperty.

References

Community reviews

Loading reviews…