Vulnerability in OpenProject (CVE-2026-44733)
Summary
Vulnerability in OpenProject (CVE-2026-44733). Confidential information can be exposed externally. 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, Business Logic Error on OpenProject through PATCH request to /api/v3/users/me permits to bypass password requirements. A password validation flaw in the change password behavior allows attackers to change a user's password only with an active session takeover. This vulnerability is fixed in 17.3.2 and 17.4.0.
Source: NIST National Vulnerability Database NVD
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-44733 has been found in OpenProject.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade OpenProject to 17.3.2 or later.
If unsure, ask your IT team or search "OpenProject CVE-2026-44733" on the vendor's site.
CVE-2026-44733 (OpenProject) — CWE-620 / CVSS v3 5.9
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-620) exists in OpenProject.
Check the vendor advisory for the affected versions of OpenProject.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
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 でアラート再発が無いか継続監視。