Quick answers
- Is CVE-2026-44731 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44731 being exploited in the wild.
- How severe is CVE-2026-44731?
- Medium severity, with a CVSS score of 4.3, published 26 June 2026.
- Which products and versions are affected?
- OpenProject GmbH OpenProject < 17.3.2, < 17.4.0.
- Is there a fix for CVE-2026-44731?
- 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-44731 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44731?
- Check whether you run OpenProject GmbH OpenProject at an affected version. 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
An information disclosure vulnerability exists in OpenProject's meetings filter feature due to improper access control (CWE-639). By manipulating the 'invited_user_id' value within the 'filters' GET parameter on the meetings endpoint, an authenticated attacker can probe user IDs. The server's response reveals whether a user ID is valid and discloses the associated user's full name. This allows for full account enumeration of the platform. The issue is fixed in versions 17.3.2 and 17.4.0.
Affected products
- opf OpenProject < 17.3.2, < 17.4.0
Timeline
- 2026-05-13: advisory: GitHub Security Advisory published by vendor
- 2026-06-26: disclosed: CVE published to NVD