Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-55810 – PHP Object Injection in Drupal Plotly.js Graphing – all versions prior to 3.0.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-55810 is a critical PHP Object Injection vulnerability in the Drupal contributed module Plotly.js Graphing, affecting all versions prior to 3.0.2. Disclosed via Drupal Security Advisory SA-CONTRIB-2026-050 on June 17, 2026, the flaw carries a CVSS v3.1 score of 9.8 (Critical) and can lead to Remote Code Execution depending on PHP gadget chains available in the target environment.

Technical details

  • Root cause: The Plotly.js Graphing module stores field data as PHP-serialized strings. Under certain conditions, an attacker can write malicious serialized data directly to a plotly_js_graph field; when the stored data is later unserialized by the application, it triggers PHP Object Injection.
  • Trigger conditions: Two prerequisites must be met: (1) the attacker must have the ability to edit a content entity with an attached plotly_js_graph field; and (2) either the Drupal JSON:API module must be enabled with the non-default "Accept all JSON:API create, read, update, and delete operations" setting, or the attacker has an alternative direct means of writing field values.
  • Attack vector: Network-accessible; exploitation is rated unauthenticated per the NVD CVSS scoring, though the Drupal advisory notes that edit-level permissions on relevant content entities are a practical prerequisite.
  • Impact: Successful exploitation results in PHP Object Injection, which — depending on available PHP gadget chains in the Drupal installation — can escalate to full Remote Code Execution, with complete confidentiality, integrity, and availability impact.

Affected software

  • Drupal Plotly.js Graphing module — all versions prior to 3.0.2

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade the Plotly.js Graphing module to version 3.0.2 or later (versions 4.0.0 and 5.0.0 are also available as current supported releases).
  • If immediate patching is not feasible:
    • Audit whether the Drupal JSON:API module is enabled with the "Accept all JSON:API create, read, update, and delete operations" option; if so, disable or restrict this setting.
    • Restrict edit permissions on all content entities that include a plotly_js_graph field to trusted, authenticated users only.
    • Review and limit access to content editing endpoints at the network layer where possible.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge