Quick answers
- Is CVE-2026-34717 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34717 being exploited in the wild.
- How severe is CVE-2026-34717?
- Critical severity, with a CVSS score of 9.9, published 2 April 2026.
- Which products and versions are affected?
- OpenProject Foundation (opf) OpenProject < 17.2.3.
- Is there a fix for CVE-2026-34717?
- A patch was published on 2026-03-31: Version 17.2.3 released with security fix. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34717 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34717?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A SQL injection vulnerability exists in OpenProject's cost reporting module within 'modules/reporting/lib/report/operator.rb'. The '=n' operator utilizes the 'parse_number_string' function, which fails to sanitize SQL metacharacters before embedding user-supplied input directly into a WHERE clause. An authenticated attacker with access to cost reports can provide malicious input via filter parameters to execute arbitrary SQL queries. This can result in unauthorized data exfiltration, modification, or deletion. The issue is resolved in version 17.2.3 by implementing proper parameterization in the SQL query.
Affected products
- OpenProject Foundation (opf) OpenProject < 17.2.3
Timeline
- 2026-03-31: patched: Version 17.2.3 released with security fix.
- 2026-03-31: advisory: Vendor advisory GHSA-5rrm-6qmq-2364 published.
- 2026-04-02: disclosed: CVE-2026-34717 published to NVD.