# CVE-2026-44732: Missing authorization in openproject

> Attackers can modify documents in unauthorized projects by manipulating the project_id parameter in API requests, requiring an upgrade to OpenProject.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-mqvv-5mvc-7pg7

## What is CVE-2026-44732?

CVE-2026-44732 is a medium-severity missing authorization vulnerability in opf openproject, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenProject is open-source, web-based project management software. Prior to 17.3.2 and 17.4.0, OpenProject exposes a document update endpoint used to modify existing documents. The target document is loaded with visibility checks and then updated. During update, attacker-controlled attributes are applied to the persisted record before authorization is enforced. As a result, a user without :manage_documents in the source project can move and modify foreign project documents by setting project_id in a single PATCH request. This vulnerability is fixed in 17.3.2 and 17.4.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-44732 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44732 is a medium-severity missing authorization vulnerability in opf openproject, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44732 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-44732/ (Markdown: https://insights.sbomify.com/CVE-2026-44732/index.md)
```

## Sources

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

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