CVE-2026-34717
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenProject is an open-source, web-based project management software. Prior to version 17.2.3, the =n operator in modules/reporting/lib/report/operator.rb:177 embeds user input directly into SQL WHERE clauses without parameterization. This issue has been patched in version 17.2.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in OpenProject's reporting module where the =n operator in modules/reporting/lib/report/operator.rb embeds unsanitized user input directly into SQL WHERE clauses at line 177, allowing attackers to manipulate database queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 17.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenProject installation and versionCheck the installed OpenProject version by running 'openproject --version' or examining the Gemfile.lock for the openproject gem versionAffected if The installed version is lower than 17.2.3
-
Locate the vulnerable operator.rb fileFind the file at modules/reporting/lib/report/operator.rb in the OpenProject installation directoryAffected if The file exists at that path in the installation
-
Inspect the =n operator implementationExamine line 177 and surrounding code in operator.rb to see if user input is directly interpolated into SQL without parameterization (look for string concatenation or interpolation in WHERE clauses)Affected if The =n operator directly embeds user input into SQL strings without using parameterized queries
-
Verify the reporting module is enabledCheck OpenProject configuration files (e.g., config/settings.yml or config/configuration.yml) or the database for enabled modules, specifically the 'reporting' moduleAffected if The reporting module is enabled and accessible to users
The environment is affected if OpenProject version is below 17.2.3 AND the reporting module is enabled AND the vulnerable =n operator code exists without proper SQL parameterization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped17.2.3
Upgrade OpenProject to version 17.2.3 or later which contains parameterized query fixes.
17.2.3
- 1. Back up your OpenProject database and installation before proceeding with any upgrade.
- 2. Upgrade OpenProject to version 17.2.3 or later by following the official upgrade documentation at https://www.openproject.org/docs/installation-and-operations/upgrading/.
- 3. Verify the upgrade was successful by logging into OpenProject and checking the version number.
- 4. Test the =n operator functionality in the reporting module to confirm the SQL injection vulnerability is patched.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34717 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data