dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-52779

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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, a cross-project IDOR / authorization context confusion in the Calendar and Team Planner modules allows a user with management permissions in one project to delete public Calendar or Team Planner Queries from another project where they do not have the corresponding management permissions. Both modules authorize the request against the project identified by :project_id in the URL, but the actual Query object is loaded later by :id from Query.visible(current_user) without verifying that the loaded Query belongs to the authorized project. As a result, an attacker can use permissions from Project A to delete shared/public Calendar or Team Planner views from Project B, causing integrity impact and limited availability impact for users relying on those shared views. 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 an IDOR (Insecure Direct Object Reference) vulnerability in OpenProject's Calendar and Team Planner modules where the authorization check uses the project ID from the URL, but the actual Query object is loaded by a separate ID without verifying it belongs to that project. A user with management permissions in one project can delete public/shared Calendar or Team Planner queries from another project where they lack permissions.

MitigationUpgrade to OpenProject version 17.3.3 or 17.4.1 which contains the patch for this authorization bypass vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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
    Access the OpenProject administration panel (typically at /admin) or check the installation's Gemfile.lock for the openproject-core version, or run 'openproject run rails runner "puts OpenProject::VERSION"' from the installation directory
    Affected if The installed version is earlier than 17.3.3 or 17.4.1 (any 17.x version before these patch releases)
  2. Verify Calendar module is enabled
    Navigate to Administration > Modules (or /admin/modules) and check if the Calendar module is listed as active for any project, or inspect the enabled_modules column in the projects database table
    Affected if Calendar module is enabled on any project where users have view_shared_queries or manage_public_queries permissions across different projects
  3. Verify Team Planner module is enabled
    Navigate to Administration > Modules and check if the Team Planner module is active, or query the enabled_modules setting for projects
    Affected if Team Planner module is enabled on any project with cross-project query sharing permissions
  4. Check for cross-project query sharing configuration
    Inspect the roles and permissions at Administration > Users and Roles. Look for users with the 'Manage public queries' or 'View shared queries' permission in one project who also have access to a different project where they lack full permissions
    Affected if A user has management permissions (delete_queries) in one project AND has access to shared/public queries from a different project where they lack the manage_public_queries permission
  5. Test vulnerable query deletion behavior
    As a user with query management in Project A, attempt to delete a shared/public query from Project B using the URL pattern /projects/A/queries/{query_id}/destroy where query_id belongs to Project B's Calendar or Team Planner
    Affected if The deletion succeeds despite the user lacking authorization over Project B's queries (confirms the IDOR is exploitable)

You are affected if running any OpenProject version below 17.3.3 or 17.4.1 with Calendar or Team Planner modules enabled, especially in multi-project environments where query sharing permissions exist across projects with different authorization levels.

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 to OpenProject version 17.3.3 or 17.4.1 which contains the patch for this authorization bypass vulnerability.

Recommended fix High confidence

OpenProject 17.3.3 or 17.4.1

  1. 1. Identify the currently installed OpenProject version by checking the application's about page or package manager.
  2. 2. If running a version prior to 17.3.3 or 17.4.1, plan for an upgrade to one of these fixed versions.
  3. 3. Review the OpenProject upgrade documentation for your specific installation method (e.g., Docker, package, source).
  4. 4. Create a backup of the OpenProject database and configuration files before proceeding.
  5. 5. Perform the upgrade following the official upgrade path for your installation method.
  6. 6. After upgrade, verify the Calendar and Team Planner modules function correctly with proper authorization checks.
Caveat Review OpenProject release notes for any breaking changes between your current version and 17.3.3/17.4.1

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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