Skip to main content
CVE-2026-24777VulnerabilityPublished

CVE-2026-24777: opf openproject · Missing Authorization

Affects opf openprojectSource CVE Database V5

0

Not known to be exploited · CVSS 6.7 Medium : upgrade to 17.0.2 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
6.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 17.0.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade opf openproject to 17.0.2.

Affected software

ProductAffectedFixed in
opfopenprojectAffected
  • <17.0.2
Fixed in
  • 17.0.2

AI-suggested

The primary mitigation is to upgrade OpenProject installations to version 17.0.2 or later, where the missing authorization check has been implemented. Organizations should audit and restrict the Manage Users permission to only trusted personnel, minimizing the number of users who can exploit this vulnerability. Implement role-based access control (RBAC) policies to enforce the principle of least privilege. Monitor user account lock/unlock activities for unusual patterns that could indicate abuse. Employ multi-factor authentication (MFA) for accounts with elevated privileges to reduce the risk of credential compromise. Regularly review and update security policies related to user management in OpenProject. In environments where immediate upgrade is not feasible, consider temporary compensating controls such as manual oversight of user lock/unlock actions or disabling the Manage Users permission where possible. Maintain up-to-date backups of user and project data to enable recovery in case of disruption.

Description

OpenProject 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.

References

Community reviews

Loading reviews…