Skip to content

GraphQL IDOR allows authenticated user to delete workspace content of other users

High
aHenryJard published GHSA-pr6m-q4g7-342c Jan 5, 2026

Package

No package listed

Affected versions

< 6.8.1

Patched versions

>= 6.8.1

Description

Summary

The GraphQL mutation "WorkspacePopoverDeletionMutation" allows users to delete workspace-related objects such as dashboards and investigation cases. However, the mutation lacks proper authorization checks to verify ownership of the targeted resources.
An attacker can exploit this by supplying an active UUID of another user. Since the API does not validate whether the requester owns the resource, the mutation executes successfully, resulting in unauthorized deletion of the entire workspace.

Impact

Loss of Critical User Data

  • Custom Dashboards often contain personalized views, metrics, and configurations tailored to specific workflows or monitoring needs.
  • Investigation Cases may include sensitive evidence, timelines, and analyst notes crucial for incident response or forensic analysis.
  • Unauthorized deletion leads to irreversible data loss, disrupting user operations and investigations.

Operational Disruption

  • Users may lose access to dashboards used for real-time monitoring or decision-making.
  • Investigations may be halted or delayed due to missing case data, affecting incident response timelines and outcomes.
  • Teams relying on shared dashboards or cases may face coordination breakdowns.

Privilege Escalation Vector

  • Attackers can use this vulnerability to target high-value users (e.g., admins, SOC analysts) by deleting their dashboards or cases.
  • This can be part of a broader attack chain to sabotage detection capabilities, hide malicious activity, or delay response.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

CVE ID

CVE-2025-61781

Weaknesses

Improper Authorization

The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Learn more on MITRE.

Authorization Bypass Through User-Controlled SQL Primary Key

The product uses a database table that includes records that should not be accessible to an actor, but it executes a SQL statement with a primary key that can be controlled by that actor. Learn more on MITRE.

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. Learn more on MITRE.

Credits