CVE-2026-32698

OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution

HIGH
7.2
CVSS Score
Published: March 18, 2026 at 09:01 PM UTC
Updated: June 17, 2026 at 10:36 AM UTC
2 products affected across 2 vendorsOpenprojectOpenproject

Using openproject by opf?

Get instant alerts when new vulnerabilities affect openproject - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.2
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 16.6.917.0.0 ≤ v < 17.0.617.1.0 ≤ v < 17.1.317.2.0
v < 16.6.9v < 17.0.6v < 17.1.3v < 17.2.1
Affected range stops below 16.6.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.0.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.2.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

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

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-89

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card