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

CVE-2026-52782

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 an IDOR through /projects/<A>/settings/project_storages/<A_ps_id> via PATCH parameter "storages_project_storage[project_folder_id]" leads to Access to Unauthorized Resources. A project-admin in one project can hijack the managed Nextcloud or OneDrive folder of another project on the same storage by writing the victim project's project_folder_id into the attacker's Storages::ProjectStorage row. The next managed-folder sync overwrites the ACL on the referenced folder with the attacker project's user list. 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 vulnerability in OpenProject's project storage settings endpoint. A project-admin can modify the PATCH parameter 'storages_project_storage[project_folder_id]' to reference another project's folder, allowing them to hijack managed Nextcloud or OneDrive folders. When the managed-folder sync occurs, it overwrites the ACL on the victim folder with the attacker's user list, granting unauthorized access.

MitigationUpgrade OpenProject to version 17.3.3 or 17.4.1 or later. If immediate patching is not possible, audit project-admin role assignments and implement monitoring on the project_storages API endpoints for suspicious parameter modifications.

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
High

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

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. Check OpenProject version
    Run 'openproject --version' or check the OpenProject administration UI under 'Administration > Information' to find the installed version number
    Affected if The installed version is earlier than 17.3.3 or earlier than 17.4.1 (for example, 17.2.x, 17.3.0-17.3.2, 17.4.0)
  2. Verify storages module is enabled
    Navigate to Administration > Modules or check the plugins directory for the 'storages' module presence in config/initializers/plugins.rb or by querying the API endpoint /api/v3/capabilities
    Affected if The storages module is listed as available and enabled in the instance
  3. Confirm project-admin role has storage settings access
    Go to Administration > Roles and Permissions and inspect the project-admin role permissions to see if 'Project storage settings' or 'manage storages' permission is granted
    Affected if The project-admin role includes permission to modify project storage settings or manage storage integrations
  4. Check if storage integrations are configured
    Look for configured Nextcloud or OneDrive integrations by querying the /api/v3/storages endpoint or navigating to Project > Settings > File storages in the UI
    Affected if At least one Nextcloud or OneDrive storage is integrated and linked to any project
  5. Inspect API access logs for suspicious parameter modification
    Review web server or OpenProject logs for PATCH/PUT requests to /api/v3/projects/:id/storages where the request body contains 'storages_project_storage[project_folder_id]' with a folder ID that differs from the project ID in the URL
    Affected if Such API calls are present in the logs, indicating potential exploitation attempts

A user is affected if they run an OpenProject version before 17.3.3 or before 17.4.1 AND have the storages module enabled with configured Nextcloud or OneDrive integrations accessible to project-admin 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. If immediate patching is not possible, audit project-admin role assignments and implement monitoring on the project_storages API endpoints for suspicious parameter modifications.

Recommended fix High confidence

OpenProject 17.3.3 or 17.4.1 (both contain the fix)

  1. 1. Identify the current OpenProject version by checking the admin interface or running `openproject --version`
  2. 2. If running a version prior to 17.3.3 or 17.4.1, plan for an upgrade to version 17.3.3 or 17.4.1
  3. 3. Create a backup of the OpenProject database and configuration files before proceeding
  4. 4. For Docker installations: pull the new image tag (e.g., `openproject:17.3.3` or `openproject:17.4.1`) and recreate containers
  5. 5. For package installations: run the appropriate package manager update command (e.g., `apt-get update && apt-get install openproject` or equivalent for your distribution)
  6. 6. After upgrade, verify the application is running and check that project storages settings are intact
  7. 7. Review audit logs to confirm no unauthorized access occurred prior to the patch
Caveat Review the OpenProject 17.3 and 17.4 release notes for any migration requirements or configuration changes that may affect your instance

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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