Skip to content

SQL Injection in Cost Reporting =n Operator via parse_number_string

Critical
oliverguenther published GHSA-5rrm-6qmq-2364 Mar 31, 2026

Package

bundler openproject (rubygems)

Affected versions

<= 15.0.0

Patched versions

None

Description

Summary

The =n operator in modules/reporting/lib/report/operator.rb:177 embeds user input directly into SQL WHERE clauses without parameterization.

Detail

new "=n", label: :label_equals do
  def modify(query, field, value)
    query.where "#{field} = #{parse_number_string(value)}"  # SQL INJECTION
    query
  end
end

parse_number_string only strips locale delimiters, not SQL metacharacters. Value is user-controlled via cost report filter params.

Impact

Authenticated user with cost report access can read/modify any database data.

Fix

query.where ["#{field} = ?", parse_number_string(value)]

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

CVE ID

CVE-2026-34717

Weaknesses

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. Learn more on MITRE.

Credits