dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-52785

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

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 · unedited
OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, there is a SQL injection in timestamps functionality. OpenProject baseline comparison allows callers to request historic work-package attributes using the timestamps parameter. This vulnerability is fixed in 17.3.3 and 17.4.1.

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 confidence

This is a SQL injection vulnerability in OpenProject's timestamps functionality within the baseline comparison feature. The timestamps parameter, used to request historic work-package attributes, does not properly sanitize user input, allowing attackers to inject malicious SQL queries.

MitigationUpgrade OpenProject to version 17.3.3 or 17.4.1 or later to patch the SQL injection vulnerability in the timestamps functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenProject installation and version
    Check the installed OpenProject version by running 'openproject --version' or inspecting the Gemfile.lock in the installation directory, or checking the package.json for enterprise installations
    Affected if Version is below 17.3.3 or between 17.3.3 and 17.4.0 (for 17.x releases)
  2. Verify baseline comparison feature is enabled
    Check if the baseline comparison module is active in OpenProject by navigating to Project > Settings > Modules, or query the 'enabled_modules' table in the database for 'baseline_comparison'
    Affected if The baseline comparison module is enabled for any project
  3. Confirm timestamps parameter is accessible
    Attempt to access the baseline comparison endpoint with a timestamps parameter, such as GET /work_packages?timestamps=2024-01-01, or inspect web server logs for requests to /work_packages with timestamps parameter
    Affected if The timestamps parameter can be passed to work package queries
  4. Check database user privileges
    Review the database user configuration in config/database.yml to determine if the OpenProject database user has elevated privileges beyond read-only
    Affected if Database user has privileges beyond what is strictly required for application operation

You are affected if running an OpenProject version below 17.3.3 or between 17.3.3 and 17.4.0 AND the baseline comparison feature is enabled and accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenProject to version 17.3.3 or 17.4.1 or later to patch the SQL injection vulnerability in the timestamps functionality.

Recommended fix High confidence

17.3.3 or 17.4.1

  1. 1. Identify the current OpenProject version by checking the administration panel or running `openproject --version`
  2. 2. If running a version prior to 17.3.3 or 17.4.1, plan for upgrade to either 17.3.3 or 17.4.1
  3. 3. Backup the existing OpenProject database and configuration files
  4. 4. For package-based installations: Run `apt-get update && apt-get install openproject` or the equivalent package manager command
  5. 5. For Docker-based installations: Pull the new image tag `openproject/openproject:17.3.3` or `openproject/openproject:17.4.1` and recreate the container
  6. 6. For source-based installations: Checkout the tag `v17.3.3` or `v17.4.1` and follow the upgrade documentation
  7. 7. Run database migrations if required: `rake db:migrate`
  8. 8. Verify the upgrade was successful by checking the OpenProject version in the administration panel
Caveat Review OpenProject release notes for version-specific migration requirements and potential breaking changes between current and target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52785 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52785 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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