dbcve.org
OpenprojectApplication

CVE-2026-30234

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 17.2.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 an open-source, web-based project management software. Prior to 17.2.0, an authenticated project member with BCF import permissions can upload a crafted .bcf archive where the <Snapshot> value in markup.bcf is manipulated to contain an absolute or traversal local path (for example: /etc/passwd or ../../../../etc/passwd). During import, this untrusted <Snapshot> value is used as file.path during attachment processing. As a result, local filesystem content can be read outside the intended ZIP scope. This results in an Arbitrary File Read (AFR) within the read permissions of the OpenProject application user. This vulnerability is fixed in 17.2.0.

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

An authenticated project member with BCF import permissions can upload a crafted .bcf archive where the <Snapshot> XML element contains an absolute or traversal path (e.g., /etc/passwd or ../../../../etc/passwd). During import, this untrusted value is used as file.path in attachment processing, enabling Arbitrary File Read within the application's read permissions.

MitigationUpgrade to OpenProject version 17.2.0 or later. If upgrading is not immediately feasible, restrict BCF import permissions to only trusted users and implement additional input validation on the Snapshot path value before attachment processing.

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
OpenprojectApplication
Affected:< 17.2.0

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify OpenProject installation
    Check for OpenProject by looking for its web interface, typical installation paths (/opt/openproject, /var/www/openproject), or check running services (ps aux | grep openproject). Also check if the default port 443/80 is serving OpenProject.
    Affected if OpenProject is not installed or not accessible on this system
  2. Determine installed OpenProject version
    Run 'openproject --version' or check the About page in the OpenProject web UI (Administration > About). If using docker, run 'docker exec <container> openproject run rake openproject:version'. Check /opt/openproject/config/version file if it exists.
    Affected if The installed version is lower than 17.2.0 (e.g., 17.1.x, 17.0.x, 16.x, etc.)
  3. Verify BCF import module is enabled
    In the OpenProject web UI, go to Administration > Plugins (or Modules). Check if the BCF (BIM Collaboration Format) module is listed and enabled for any project. The module typically appears under 'Modules' in project settings.
    Affected if BCF module is enabled and accessible to project members
  4. Check BCF import permissions configuration
    Navigate to Administration > Roles and Permissions. For each role, examine the permissions under 'Project' or 'File' categories. Look specifically for 'BCF import' or 'Import BCF' permission. Check which roles have this permission assigned.
    Affected if Authenticated project members (non-admin roles) have BCF import permission enabled

A user is affected if they run OpenProject version below 17.2.0 with the BCF module enabled and at least one authenticated project member role has BCF import permissions granted.

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
Upgrade available Upgrade to 17.2.0 or later
Fixed in 17.2.0
Interim mitigation

Upgrade to OpenProject version 17.2.0 or later. If upgrading is not immediately feasible, restrict BCF import permissions to only trusted users and implement additional input validation on the Snapshot path value before attachment processing.

Recommended fix High confidence

17.2.0

  1. 1. Plan maintenance window for the OpenProject upgrade
  2. 2. Backup the existing OpenProject database and installation
  3. 3. Upgrade OpenProject to version 17.2.0 or later (e.g., 17.2.0, 17.2.1, latest stable)
  4. 4. Verify the upgrade was successful by checking the OpenProject version in the UI or via CLI
  5. 5. Confirm BCF import functionality works correctly with legitimate .bcf files

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

Fix this in Openproject Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30234 — 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-30234 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