Quick answers
- Is CVE-2026-52779 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52779 being exploited in the wild.
- How severe is CVE-2026-52779?
- Medium severity, with a CVSS score of 5.4, published 26 June 2026.
- Which products and versions are affected?
- opf OpenProject < 17.3.3, >= 17.4.0 < 17.4.1.
- Is there a fix for CVE-2026-52779?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-52779 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-52779?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A cross-project IDOR / authorization context confusion exists in the Calendar and Team Planner modules of OpenProject. The application performs project-based authorization using the ':project_id' provided in the URL, but subsequently loads the target 'Query' object by its ':id' without verifying that the object actually belongs to the authorized project. An attacker with management permissions in 'Project A' can send a DELETE request referencing 'Project A' in the URL while targeting the ID of a public Calendar or Team Planner view belonging to 'Project B'. This allows the attacker to bypass intended permission boundaries and delete shared views they do not own. The issue is fixed in versions 17.3.3 and 17.4.1.
Affected products
- opf OpenProject < 17.3.3, >= 17.4.0 < 17.4.1
Timeline
- 2026-06-10: advisory: Original GitHub security advisory published
- 2026-06-26: disclosed: NVD publication date