Cross-Site Scripting (XSS) in OpenProject (CVE-2026-44696)
Summary
Cross-site scripting in OpenProject (CVE-2026-44696). Data can be tampered with by attackers. Mitigation: upgrade to 17.4.0 or later.
Original description
The description as published by the source.
OpenProject is open-source, web-based project management software. Prior to 17.4.0, OpenProject's rich text (markdown) rendering pipeline uses Sanitize::Config::RELAXED[:css] for inline style sanitization. This configuration permits essentially all CSS properties in style attributes on permitted HTML elements (figure, img, table, th, tr, td). This allows any authenticated user with write access to formattable text fields (work package descriptions, comments, project descriptions, news) to inject CSS This vulnerability is fixed in 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-44696 has been found in OpenProject.
Data can be tampered with by attackers. CVSS score: 5.7/10.
What to do: upgrade OpenProject to 17.4.0 or later.
If unsure, ask your IT team or search "OpenProject CVE-2026-44696" on the vendor's site.
CVE-2026-44696 (OpenProject) — CWE-79 / CVSS v3 5.7
Attack vector: remote (network-reachable)
Patched: 17.4.0 — 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.
Cross-site scripting (XSS) (CWE-79) exists in OpenProject.
Check the vendor advisory for the affected versions of OpenProject.
Severity: Medium (CVSS 5.7/10). Data can be tampered with by attackers.
Update to 17.4.0.
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.4.0ステージング環境で 17.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov