CVE-2025-61781
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 · uneditedOpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to version 6.8.1, 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. Version 6.8.1 fixes the issue.
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 · high confidenceOpenCTI versions prior to 6.8.1 contain an Insecure Direct Object Reference (IDOR) vulnerability in the GraphQL mutation 'WorkspacePopoverDeletionMutation'. The mutation allows deletion of workspace objects (dashboards, investigation cases) but fails to verify that the requesting user owns the targeted resource. An authenticated attacker can delete any workspace by providing its UUID, resulting in unauthorized mass deletion of other users' workspaces.
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< 6.8.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check OpenCTI versionRetrieve the installed OpenCTI version from the platform interface (typically visible in the footer of the web UI), via the Docker container labels, or by querying the API endpoint /api/version. Compare this version number to the 6.8.1 threshold.Affected if The installed version is below 6.8.1 (e.g., 6.8.0, 6.7.x, etc.)
-
Confirm GraphQL API is accessibleVerify that the GraphQL endpoint (typically at /graphql) is reachable and accepts authenticated requests. This can be done by attempting a basic GraphQL query with valid credentials.Affected if The GraphQL API is exposed and accepts authenticated requests, enabling the vulnerable mutation to be invoked
-
Identify authenticated user permissionsExamine the OpenCTI user roles and permissions to determine if standard users can access the workspace deletion mutation. Check if multiple users exist in the platform who could potentially delete other users workspaces.Affected if Multiple users have authenticated access and at least one user role permits access to the WorkspacePopoverDeletionMutation without ownership verification
You are affected if your OpenCTI installation version is below 6.8.1 and the GraphQL API is accessible to authenticated users, allowing the IDOR vulnerability to be exploited for unauthorized workspace deletion.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.8.1
Upgrade OpenCTI to version 6.8.1 or later, which adds proper authorization checks to verify resource ownership before deletion. If immediate upgrade is not possible, restrict GraphQL API access to trusted users only.
6.8.1
- Verify current OpenCTI version using platform administration interface or API
- Backup the OpenCTI database and configuration files before upgrading
- Upgrade OpenCTI to version 6.8.1 following the standard upgrade procedure for your deployment method (Docker, Kubernetes, or bare metal)
- After upgrade completes, verify the WorkspacePopoverDeletionMutation now performs proper ownership validation
- Confirm that users can no longer delete workspaces belonging to other users by supplying arbitrary UUIDs
- Test that legitimate workspace deletion still functions correctly for resource owners
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61781 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-61781 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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