dbcve.org
Plotly.js GraphingDrupal extension · Plotly

CVE-2026-55810

HIGH · 8.1 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 3.0.2 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 6 weeks old

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
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.

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

Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Drupal Plotly.js Graphing module (versions 0.0.0-3.0.2) allows Object Injection. This PHP object injection vulnerability likely involves unserialization of user-controlled data, potentially enabling remote code execution if exploitable classes with magic methods are present in the application.

MitigationUpdate the Plotly.js Graphing module to a patched version once available, or disable the module as a temporary measure. Review code for unsafe use of unserialize(), dynamic property assignment, or similar patterns that allow object attribute manipulation.

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.js GraphingDrupal extension
Affected:< 3.0.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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. Locate the Plotly.js Graphing module installation
    Search for the plotly module directory in your Drupal installation under modules/contrib/ or modules/custom/, or check your Drupal database for the plotly module in the system table.
    Affected if The plotly module directory or database entry exists, indicating the module is installed.
  2. Identify the installed module version
    Check the plotly.info.yml file or composer.json within the plotly module directory for the version number, or run: drush pm:list --filter=plotly
    Affected if The version is 3.0.2 or lower, or the version cannot be determined (indicating an unpatched installation).
  3. Determine if the module is enabled
    Run: drush state-get system.module_enabled or check the status column in the Drupal system table for the plotly module.
    Affected if The module is listed as enabled in Drupal's module storage.
  4. Check for exposed Plotly input handlers
    Review Drupal permissions and any content types, forms, or custom endpoints that accept Plotly configuration input. Look for code that passes user input directly to Plotly rendering functions without sanitization.
    Affected if User-supplied input can reach Plotly object/attribute parameters without strict validation.

You are affected if the Plotly.js Graphing module is installed and enabled at version 3.0.2 or lower, and user input can influence Plotly object properties without strict property whitelisting.

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

Update the Plotly.js Graphing module to a patched version once available, or disable the module as a temporary measure. Review code for unsafe use of unserialize(), dynamic property assignment, or similar patterns that allow object attribute manipulation.

Recommended fix Moderate confidence

3.0.2 or later

  1. Identify all projects or Drupal installations that include the Plotly.js Graphing library
  2. Locate the plotly.js library file in your codebase (typically in libraries/ or node_modules/)
  3. Check the current version of plotly.js by inspecting the package.json or library files
  4. Upgrade the Plotly.js library to version 3.0.2 or later by running npm install [email protected] or by downloading the updated library from the official Plotly distribution
  5. Clear any cached assets or compiled bundles in your project
  6. Test the application to ensure the upgrade does not break existing functionality
  7. Deploy the updated library to all production environments

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

Fix this in Plotly.js Graphing Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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