CVE-2026-24777
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 · uneditedOpenProject is an open-source, web-based project management software. Prior to 17.0.2, users with the Manage Users permission can lock and unlock users. This functionality should only be possible for users of the application, but they were not supposed to be able to lock application administrators. Due to a missing permission check this logic was not enforced. The problem was fixed in OpenProject 17.0.2The problem was fixed in OpenProject 17.0.2.
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 confidenceOpenProject versions prior to 17.0.2 contain a missing authorization check that allows users with the Manage Users permission to lock and unlock administrative accounts. This privilege escalation occurs because the application fails to enforce that non-admin users with Manage Users permissions cannot modify administrator 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< 17.0.2CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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.
-
Identify OpenProject versionAccess the OpenProject administration panel, navigate to Administration > Information, or check the package/version file in the OpenProject installation directoryAffected if The installed version is any version prior to 17.0.2
-
Verify Manage Users permission existsIn OpenProject admin panel, go to Users and Roles > Roles, or check the roles configuration for any role that includes the 'Manage Users' permissionAffected if Any role in the system has the Manage Users permission enabled for non-admin users
-
Check for non-admin users with Manage Users roleIn Administration > Users, filter or search for users assigned to a role with Manage Users permission, and verify if any of these users are not marked as administratorsAffected if There are non-administrative users assigned a role that includes Manage Users permission
-
Confirm presence of administrator accountsIn Administration > Users, identify accounts marked as 'Administrator' or check the admin flag in the user database tableAffected if There exists at least one administrator account in the system
The environment is affected if OpenProject version is below 17.0.2 AND there exist non-admin users with the Manage Users permission who could potentially lock admin 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 · scoped17.0.2
Upgrade to OpenProject version 17.0.2 or later which includes the missing permission check preventing non-admin users from locking admin accounts.
17.0.2
- Verify current OpenProject version using admin interface or command line
- Backup the current database and configuration files
- Consult OpenProject upgrade documentation for your deployment method (Docker, package, or source)
- Stop the OpenProject service
- Upgrade to version 17.0.2 or later following the official upgrade guide
- Restart the OpenProject service
- Verify the upgrade was successful and test that the authorization fix works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24777 — 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-2026-24777 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