CyberSecBulletin
CVE-2026-55810NVD status: Analyzed

Plotly.js Graphing: Improperly Controlled Modification of Dynamically-Determined Object Attributes

Published Updated By the CyberSecBulletin desk

CVE-2026-55810 is a high-severity improperly controlled modification of dynamically-determined object attributes vulnerability in Plotly.js Graphing from Drupal, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 3.0.2 as the first without the flaw, so updating Plotly.js Graphing to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.43% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Plotly.js Graphing to 3.0.2 or a later version.
  2. Read the advisory on drupal.org for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
DrupalPlotly.js Graphingbefore 3.0.23.0.2

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by CISA (ADP).

Official description

Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Drupal Plotly.js Graphing allows Object Injection. This issue affects Plotly.js Graphing versions: from 0.0.0 to 3.0.2.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improperly Controlled Modification of Dynamically-Determined Object Attributes

The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.

How developers prevent this class of flaw

  • If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists. For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment.
  • If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
  • For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.

More Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerabilities (CWE-915)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerabilities

Spotted an error? Tell us.