dbcve.org
OpenctiApplication · Citeum

CVE-2025-24977

CRITICAL · 9.1 CVSS v3.1 Published 2025-05-05
Fix available
A fix is available. Upgrade to 6.4.11 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
OpenCTI is an open cyber threat intelligence (CTI) platform. Prior to version 6.4.11 any user with the capability `manage customizations` can execute commands on the underlying infrastructure where OpenCTI is hosted and can access internal server side secrets by misusing the web-hooks. Since the malicious user gets a root shell inside a container this opens up the the infrastructure environment for further attacks and exposures. Version 6.4.11 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 confidence

OpenCTI prior to version 6.4.11 contains a command injection vulnerability where users with the 'manage customizations' capability can abuse webhooks to execute arbitrary commands on the underlying containerized infrastructure, achieving root shell access and exposing internal server-side secrets.

MitigationUpgrade OpenCTI to version 6.4.11 or later which contains the fix for this vulnerability.

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
OpenctiApplication
Affected:>= 6.4.8, < 6.4.11

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenCTI version
    Log into the OpenCTI administration interface and navigate to the 'About' or 'Settings' page to view the installed version. Alternatively, check the version in the Docker container or deployment configuration if self-hosted.
    Affected if The installed version is 6.4.8, 6.4.9, or 6.4.10.
  2. Verify version is in affected range
    Compare the identified version against the affected range: versions greater than or equal to 6.4.8 and less than 6.4.11 are vulnerable.
    Affected if The version falls within >= 6.4.8 and < 6.4.11.
  3. Review user roles with manage customizations capability
    Access the OpenCTI user management section and inspect all roles to identify which users or groups have the 'manage customizations' capability assigned.
    Affected if Any user account other than trusted administrators has the 'manage customizations' capability enabled.
  4. Audit webhook configurations
    Navigate to the customizations or integrations settings panel and examine any webhook definitions for suspicious or unexpected endpoint URLs, especially those pointing to internal infrastructure or shell execution patterns.
    Affected if Webhooks exist that were not created by a trusted administrator or contain unexpected external endpoints.

A user is affected if their OpenCTI installation is version 6.4.8, 6.4.9, or 6.4.10 and any user possesses the 'manage customizations' capability.

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

Upgrade OpenCTI to version 6.4.11 or later which contains the fix for this vulnerability.

Recommended fix High confidence

6.4.11

  1. Verify the current OpenCTI version by checking the container or installation
  2. Review the OpenCTI 6.4.11 release notes for any migration requirements or breaking changes
  3. Back up the current OpenCTI database and configuration
  4. Stop the running OpenCTI services
  5. Pull or fetch the updated OpenCTI version 6.4.11 container image or package
  6. Update the deployment configuration to use version 6.4.11
  7. Start the OpenCTI services with the new version
  8. Verify the upgrade was successful by checking the version in the UI or API
Caveat Check OpenCTI 6.4.11 release notes for any breaking changes or migration steps before upgrading

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

Fix this in Opencti Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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