LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46308: In Plotly plotly.js before 2.25.2, plot API calls have a risk of __proto__ being polluted in expandObjectPa...

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

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Plotly.js versions before 2.25.2 are reported to allow prototype pollution through plot API handling. Specially shaped plotting inputs may alter shared JavaScript object behavior inside an application. The CVSS rating is critical, but the provided sources do not show public exploitation or impacted downstream packages.

Executive priority

Treat as high-priority patching for externally reachable applications that render Plotly charts from untrusted or user-controlled data. Deprioritize only after confirming no vulnerable plotly.js is deployed.

Technical view

The CVE describes CWE-1321 prototype pollution in expandObjectPaths or nestedProperty reached by plot API calls in plotly.js before 2.25.2. The record assigns CVSS 3.1 9.8: network, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely where applications directly load plotly.js versions before 2.25.2. The bundle does not enumerate exact CPEs or downstream affected packages, so validation should be based on dependency inventory and bundled JavaScript versions.

Exploitation context

The supplied data says KEV is false and provides no cited evidence of active exploitation. Risk comes from the severe CVSS characteristics and the prototype pollution class, not from confirmed in-the-wild attacks in these sources.

Researcher notes

Evidence is limited to the CVE description, CVSS metadata, Plotly release reference, and related Plotly.R issue. Do not assume R, Python, or other wrappers are affected without confirming their shipped or loaded plotly.js version.

Mitigation direction

  • Upgrade plotly.js to version 2.25.2 or later where present.
  • Check Plotly release notes and vendor guidance before deploying mitigations.
  • Inventory bundled or vendored plotly.js copies in web assets.
  • Review dependent Plotly wrappers for their embedded or resolved plotly.js version.

Validation and detection

  • Search dependency manifests for plotly.js versions before 2.25.2.
  • Inspect production bundles for vendored plotly.js copies.
  • Confirm runtime pages load the expected patched Plotly asset.
  • Review scanner findings against actual deployed JavaScript, not only source manifests.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-46308 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-46308Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-1321

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1321 · source CWE mapping

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs