Skip to main content
VulnerabilityPublished

CVE-2026-32698: opf openproject · SQL Injection

Affects opf openprojectSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical · fixed in 17.2.1 : patch opf openproject as a priority.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 17.2.1, 17.1.3, 17.0.6 +1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade openproject to 17.2.1, 17.1.3, 17.0.6 or 16.6.9; opf/openproject to 16.6.9.

Affected software

ProductAffectedFixed in
opfopenprojectAffected
  • >=17.2.0 <17.2.1
Fixed in
  • 17.2.1
opfopenprojectAffected
  • >=17.1.0 <17.1.3
Fixed in
  • 17.1.3
opfopenprojectAffected
  • >=17.0.0 <17.0.6
Fixed in
  • 17.0.6
opfopenprojectAffected
  • <16.6.9
Fixed in
  • 16.6.9
GitHubopf/openprojectpkg:github/opf/openprojectOther threatsAffected
  • <16.6.9
Fixed in
  • 16.6.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade OpenProject to versions 16.6.9, 17.0.6, 17.1.3, or 17.2.1, depending on their current version branch. Restrict administrator privileges strictly and audit existing custom fields for suspicious or malformed entries. Implement database activity monitoring to detect unusual SQL queries related to custom fields or project identifiers. Harden the server environment by limiting filesystem permissions to prevent unauthorized git repository checkouts outside intended directories. Employ application-level input validation and sanitization for all user-controlled inputs, especially custom fields and project identifiers. Regularly review and update OpenProject and all dependencies to incorporate security patches. Consider network segmentation and firewall rules to limit access to the OpenProject server. Finally, monitor logs for signs of exploitation attempts, such as unexpected SQL errors or unusual repository checkout paths.

Description

CVE-2026-32698 is a critical SQL injection vulnerability in OpenProject versions prior to 16.6.9, 17.0.6, 17.1.3, and 17.2.1. It arises from improper sanitization of a custom field's name used in Cost Reports, allowing attackers with administrator privileges to execute arbitrary SQL commands.

References

Community reviews

Loading reviews…