# CVE-2026-30236: OpenProject users that are not project members can be used to calculate Labor Budget, leaking their global hourly rate

> Attackers can view global hourly rates of non-project members by exploiting missing membership checks in budget planning features.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 11 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-p747-569x-3v3f

## What is CVE-2026-30236?

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

### Official description

OpenProject is an open-source, web-based project management software. Prior to 17.2.0, when editing a project budget and planning the labor cost, it was not checked that the user that was planned in the budget is actually a project member. This exposed the user's default rate (if one was set up) to users that should only see that information for project members. Also, the endpoint that handles the pre-calculation for the frontend to display a preview of the costs, while it was being entered, did not properly validate the membership of the user as well. This also allowed to calculate costs with the default rate of non-members. This vulnerability is fixed in 17.2.0.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Openproject Openproject.

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

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

## Is CVE-2026-30236 being exploited?

There is no known exploitation of CVE-2026-30236 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-30236 and fix it if it is affected.

What it is: CVE-2026-30236 is a medium-severity missing authorization vulnerability in opf openproject, published on 11 Mar 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-30236 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-30236/ (Markdown: https://insights.sbomify.com/CVE-2026-30236/index.md)
```

## Sources

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

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