Vulnerability in OpenProject (CVE-2026-44734)
Summary
Vulnerability in OpenProject (CVE-2026-44734). Data can be tampered with by attackers. Mitigation: upgrade to 17.3.2 or later.
Original description
The description as published by the source.
OpenProject is open-source, web-based project management software. Prior to 17.3.2 and 17.4.0, a Missing Authorization vulnerability exists in OpenProject's CostReportsController. The rename and update actions allow any authenticated user to modify the name, filters, and grouping of any Public cost report in the system without verifying ownership or permission level. An attacker who discovers or guesses a public report's numeric ID can rename or overwrite its filter configuration without any warning to the report's owner. This vulnerability is fixed in 17.3.2 and 17.4.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44734 has been found in OpenProject.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade OpenProject to 17.3.2 or later.
If unsure, ask your IT team or search "OpenProject CVE-2026-44734" on the vendor's site.
CVE-2026-44734 (OpenProject) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 17.3.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in OpenProject.
Check the vendor advisory for the affected versions of OpenProject.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 17.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'OpenProject' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'OpenProject' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OpenProjectを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade OpenProject to 17.3.2ステージング環境で 17.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov