# CVE-2026-34717: OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string

> Attackers can inject SQL via the =n operator in cost reporting to read or modify database contents in OpenProject.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H`)
- **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:** 2 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-5rrm-6qmq-2364

## What is CVE-2026-34717?

CVE-2026-34717 is a critical SQL injection vulnerability in opf openproject, published on 2 Apr 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 version 17.2.3, the =n operator in modules/reporting/lib/report/operator.rb:177 embeds user input directly into SQL WHERE clauses without parameterization. This issue has been patched in version 17.2.3.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Openproject Openproject.

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

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

## Is CVE-2026-34717 being exploited?

There is no known exploitation of CVE-2026-34717 in the wild and no public exploit code.

Public exploit code:

- Boolean-based Blind SQLi exploit for CVE-2026-34717 (OpenProject 17.2.0)Boolean-based Blind SQLi exploit for CVE-2026-34717 (OpenProject 17.2.0) (github_poc): https://github.com/quanlevan1207/cve-2026-34717-exploit

## Other vulnerabilities in opf openproject

- [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)
- [CVE-2026-22600](https://insights.sbomify.com/CVE-2026-22600/): OpenProject is Vulnerable to Arbitrary File Read via ImageMagick SVG Coder (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34717 and fix it if it is affected.

What it is: CVE-2026-34717 is a critical SQL injection vulnerability in opf openproject, published on 2 Apr 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-34717 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-34717/ (Markdown: https://insights.sbomify.com/CVE-2026-34717/index.md)
```

## Sources

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

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