dbcve.org
OpenprojectApplication

CVE-2026-30239

HIGH · 7.1 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 17.2.0 or later.
See remediation →
77/100
Remediation priority · High
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, when budgets are deleted, the work packages that were assigned to this budget need to be moved to a different budget. This action was performed before the permission check on the delete action was executed. This allowed all users in the application to delete work package budget assignments. 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

OpenProject prior to 17.2.0 has a broken access control vulnerability in budget deletion. When budgets are deleted and work packages need reassignment to a different budget, this reassignment action executes BEFORE the permission check on the delete action, allowing any user to modify work package budget assignments without proper authorization.

MitigationUpgrade OpenProject to version 17.2.0 or later, which includes the fix to perform permission validation before the budget reassignment logic.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 version
    Locate the installed OpenProject version by accessing the admin interface or checking the version file/banner in the application
    Affected if The installed version is lower than 17.2.0 (e.g., 17.1.x, 17.0.x, or earlier)
  2. Verify budget module is active
    Check if the budgets module is enabled in the project or global settings where plugins and modules are configured
    Affected if Budgets module is enabled and budgets exist in the system
  3. Review budget-related permissions
    Inspect the role and permission settings to see which roles have delete permissions on budgets and reassign work package budget assignments
    Affected if Any role grants delete permission on budgets without requiring additional authorization checks
  4. Confirm user role assignment
    Identify if your user account or any role you hold has budget deletion capabilities
    Affected if Your user account is assigned a role that includes budget deletion permissions

You are affected if your OpenProject version is below 17.2.0, the budgets module is enabled, and your user role includes budget deletion permissions that could allow unauthorized reassignment of work package budgets.

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 OpenProject to version 17.2.0 or later, which includes the fix to perform permission validation before the budget reassignment logic.

Recommended fix High confidence

17.2.0

  1. 1. Back up your OpenProject database and configuration files before proceeding with any upgrade.
  2. 2. Stop the OpenProject service to prevent data integrity issues during upgrade.
  3. 3. For package-based installations: Update your package repository and install the new version using your package manager (apt-get, yum, etc.).
  4. 4. For Docker-based installations: Pull the new OpenProject image version 17.2.0 and recreate your containers.
  5. 5. Run the database migration command (typically 'openproject run rake db:migrate' or via the web interface).
  6. 6. Restart the OpenProject service.
  7. 7. Verify the upgrade was successful by checking the version in the admin panel and testing budget deletion functionality.

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

Fix this in Openproject Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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