CVE-2025-24887
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 cyber threat intelligence platform. In versions starting from 6.4.8 to before 6.4.10, the allow/deny lists can be bypassed, allowing a user to change attributes that are intended to be unmodifiable by the user. It is possible to toggle the `external` flag on/off and change the own token value for a user. It is also possible to edit attributes that are not in the allow list, such as `otp_qr` and `otp_activated`. If external users exist in the OpenCTI setup and the information about these users identities is sensitive, the above vulnerabilities can be used to enumerate existing user accounts as a standard low privileged user. This issue has been patched in version 6.4.10.
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 6.4.8 through 6.4.9 contain an authorization bypass vulnerability where the allow/deny lists for user attribute modifications can be circumvented. Authenticated users can toggle the external flag, modify their own token values, and edit sensitive attributes like otp_qr and otp_activated that should be restricted. This allows low-privileged users to enumerate external user accounts.
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.4.8, <= 6.4.10CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify installed OpenCTI versionCheck the OpenCTI application version through the UI (usually in Settings > Information) or by querying the backend/API for version metadataAffected if The installed version is 6.4.9 or 6.4.10 (versions greater than 6.4.8 and less than or equal to 6.4.10)
-
Verify user authentication is enabledConfirm that OpenCTI has user authentication configured and users can log in to the platformAffected if Users have active accounts and can authenticate to OpenCTI
-
Check for non-administrator user accountsReview the user management section to identify if there are users with standard or limited roles (non-admin) in the systemAffected if There are authenticated users with standard or limited privileges who could potentially modify their own user attributes
-
Inspect user attribute modification permissionsAttempt to access or query user profile modification features (such as API endpoints or UI forms for editing own user attributes) to see if lower-privileged users can access themAffected if Non-admin users can access features to modify their own user attributes including the external flag, token values, otp_qr, or otp_activated attributes
-
Check for sensitive attribute exposureReview API responses or user interface elements when a standard user views or edits their profile to see if sensitive attributes like otp_qr or otp_activated are exposed or editableAffected if Sensitive attributes (otp_qr, otp_activated) are visible or modifiable by non-admin users through the application
Your environment is affected if you are running OpenCTI version 6.4.9 or 6.4.10 and have non-administrative users who can access user attribute modification features for their own accounts.
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 · scopedUpgrade OpenCTI to version 6.4.10 or later to patch the allow/deny list bypass vulnerability.
6.4.10
- 1. Back up the current OpenCTI installation and database before upgrading.
- 2. Upgrade OpenCTI to version 6.4.10.
- 3. Verify that the allow/deny list bypass vulnerability is resolved by confirming users can no longer modify restricted attributes like `external`, `otp_qr`, `otp_activated`, or tokens outside the allowed list.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24887 — 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-24887 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