# CVE-2026-24777: OpenProject has Improper Access Control on User Management allows user managers to lock admin accounts

> User managers can lock administrator accounts due to missing permission checks, potentially causing denial of service or privilege escalation.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-fq66-cwg6-qq69

## What is CVE-2026-24777?

CVE-2026-24777 is a medium-severity missing authorization vulnerability in opf openproject, published on 9 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-24777?

It affects 1 product.


Products: Openproject Openproject.

## How do I fix CVE-2026-24777?

No fix has been published for CVE-2026-24777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24777 being exploited?

There is no known exploitation of CVE-2026-24777 in the wild and no public exploit code.

## Other vulnerabilities in opf openproject

- [CVE-2026-34717](https://insights.sbomify.com/CVE-2026-34717/): OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string (critical 9.9)
- [CVE-2026-25763](https://insights.sbomify.com/CVE-2026-25763/): Command Injection on OpenProject repositories leads to Remote Code Execution (critical 9.4)
- [CVE-2026-24685](https://insights.sbomify.com/CVE-2026-24685/): OpenProject has Argument Injection on Repository module that allows Arbitrary File Write (critical 9.4)
- [CVE-2026-32698](https://insights.sbomify.com/CVE-2026-32698/): OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution (critical 9.1)
- [CVE-2026-32703](https://insights.sbomify.com/CVE-2026-32703/): OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24777 and fix it if it is affected.

What it is: CVE-2026-24777 is a medium-severity missing authorization vulnerability in opf openproject, published on 9 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24777 in the wild and no public exploit code.

Affected product: opf openproject. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24777/ (Markdown: https://insights.sbomify.com/CVE-2026-24777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24777
- OSV: https://osv.dev/vulnerability/CVE-2026-24777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24777/
Summaries are generated and may contain mistakes; the official description above is the record.