CVE-2024-26139
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 allowing organizations to manage their cyber threat intelligence knowledge and observables. Due to lack of certain security controls on the profile edit functionality, an authenticated attacker with low privileges can gain administrative privileges on the web application.
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 · moderate confidenceOpenCTI suffers from an IDOR (Insecure Direct Object Reference) or broken access control vulnerability in its profile edit functionality. An authenticated user with low-level privileges can manipulate their profile to gain administrative access to the web application due to missing or insufficient authorization checks on the profile modification endpoint.
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<= 5.12.31CVSS 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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 OpenCTI installation and versionLocate the OpenCTI application and determine its installed version number by checking the application's about page, package manifest, or version file provided by the softwareAffected if The installed version is 5.12.31 or lower
-
Verify user role configurationAccess the OpenCTI administration panel and review the roles assigned to standard or low-privilege user accounts to confirm the role hierarchyAffected if Low-privilege users have accounts with modifiable role attributes in the system
-
Examine profile modification endpointUsing an authenticated low-privilege user session, inspect the HTTP requests and responses when accessing the profile edit functionality; check if role or permission fields are present in the profile modification form or API payloadAffected if The profile edit endpoint exposes role or permission fields that can be manipulated by low-privilege users
-
Test for privilege escalationAs a low-privilege user, attempt to modify the profile request to include administrative role parameters or elevated permission values, then observe whether the system accepts the modificationAffected if The system allows a low-privilege user to successfully change their own role to administrator through profile modification
A user is affected if they are running OpenCTI version 5.12.31 or lower AND the profile edit functionality permits low-privilege users to modify role attributes, allowing unauthorized privilege escalation.
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 · scopedImplement proper role-based access control (RBAC) and authorization validation on all profile edit endpoints to ensure users cannot escalate privileges beyond their assigned role; enforce server-side validation that low-privilege users cannot modify role/permission attributes.
OpenCTI version 5.12.32 or later
- 1. Back up your current OpenCTI installation and database
- 2. Verify your current version is <= 5.12.31 by checking the OpenCTI platform or docker-compose.yml
- 3. Update OpenCTI to version 5.12.32 or later using your deployment method (docker-compose update, helm upgrade, etc.)
- 4. After update, verify the new version is running: docker ps or check the UI footer
- 5. Test that the profile edit functionality now properly enforces authorization controls
- 6. Confirm low-privilege users can no longer escalate to administrative privileges
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26139 — 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-2024-26139 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