OpenProject SQL Injection Vulnerability (CVE-2026-34717)
OpenProject versions before 17.2.3 are susceptible to SQL injection due to improper input sanitization in the '=n' operator, potentially allowing remote attackers to execute arbitrary SQL commands.
OpenProject, a web-based project management software, is vulnerable to SQL injection in versions prior to 17.2.3. The vulnerability lies within the =n operator located in modules/reporting/lib/report/operator.rb:177. This operator improperly handles user input by directly embedding it into SQL WHERE clauses without adequate parameterization. An attacker could leverage this flaw to inject malicious SQL code, potentially leading to unauthorized data access, modification, or deletion. The vulnerability was reported on April 2, 2026, and patched in version 17.2.3. Organizations using vulnerable versions of OpenProject are at risk of data breaches and system compromise.
Attack Chain
- An attacker identifies an OpenProject instance running a version prior to 17.2.3.
- The attacker crafts a malicious HTTP request targeting an endpoint that utilizes the vulnerable
=noperator within themodules/reporting/lib/report/operator.rbfile. - The malicious request injects SQL code through a parameter processed by the vulnerable operator.
- The OpenProject application executes the attacker-controlled SQL code against the database due to the lack of input sanitization.
- The attacker bypasses authentication or authorization checks by manipulating the SQL query.
- The attacker retrieves sensitive data from the database, such as user credentials or project information.
- The attacker may modify data within the database, potentially altering project configurations or injecting malicious content.
- The attacker achieves complete database compromise, potentially leading to a full system takeover if database privileges are sufficient.
Impact
Successful exploitation of this SQL injection vulnerability can lead to significant data breaches, potentially exposing sensitive project data, user credentials, and confidential information. The impact ranges from unauthorized data access and modification to complete database compromise. Depending on the database privileges, this could lead to full system takeover. Organizations in various sectors utilizing vulnerable versions of OpenProject could be affected, resulting in financial losses, reputational damage, and legal liabilities. The CVSS v3.1 base score for this vulnerability is 9.9 (Critical).
Recommendation
- Upgrade OpenProject instances to version 17.2.3 or later to patch the SQL injection vulnerability (CVE-2026-34717).
- Monitor web server logs for suspicious HTTP requests targeting the vulnerable endpoint (
modules/reporting/lib/report/operator.rb) that contain SQL injection attempts. Deploy the provided Sigma ruleDetect OpenProject SQL Injection Attemptto detect potential exploitation. - Implement a web application firewall (WAF) to filter out malicious requests and prevent SQL injection attacks.
- Review and harden database access controls to minimize the impact of potential SQL injection attacks.
- Enable and monitor audit logs for database activity to detect any unauthorized data access or modification.
Detection coverage 2
Detect OpenProject SQL Injection Attempt
criticalDetects potential SQL injection attempts targeting OpenProject instances by identifying suspicious patterns in HTTP requests.
Detect OpenProject Version Check via HTTP Request
lowDetects requests to common OpenProject version check files.
Detection queries are kept inside the platform. Get full rules →
Indicators of compromise
1
| Type | Value |
|---|---|
| [email protected] |