LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23721: OpenProject users with "View Members" permission in any project can view all Group memberships

OpenProject is an open-source, web-based project management software. When using groups in OpenProject to manage users, the group members should only be visible to users that have the View Members permission in any project that the group is also a member of. Prior to versions 17.0.1 and 16.6.5, due to a failed permission check, if a user had the View Members permission in any project, they could enumerate all Groups and view which other users are part of the group. The issue has been fixed in OpenProject 17.0.1 and 16.6.5. No known workarounds are available.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

OpenProject may expose group membership information to users who should not see it. A logged-in user with “View Members” permission in any project could list all groups and see their members. This is a confidentiality issue, not a data modification or service outage issue.

Executive priority

Prioritize remediation in the normal patch cycle unless group membership reveals sensitive teams or customer/project relationships. In those environments, accelerate the upgrade because the issue can expose internal structure to ordinary authenticated users.

Technical view

CVE-2026-23721 is a CWE-862 missing authorization flaw in OpenProject group membership visibility checks. Before 16.6.5 and in 17.0.0, a low-privileged authenticated user with any project-level “View Members” permission could enumerate all groups and view user membership. CVSS 3.1 score is 4.3.

Likely exposure

Exposure applies to OpenProject versions prior to 16.6.5 and version 17.0.0 when groups are used to manage users. Risk is higher where group membership reveals sensitive teams, roles, projects, or organizational structure.

Exploitation context

The issue is network-accessible and requires a logged-in user with low privileges. The provided sources do not report active exploitation, and it is not listed as KEV in the supplied data. No public workaround is named in the advisory.

Researcher notes

The advisory states the intended rule: group members should only be visible to users with “View Members” in a project where that group is also a member. The failed permission check broadened visibility to all groups. Sources name fixed versions but no workaround.

Mitigation direction

  • Upgrade OpenProject to 17.0.1 or 16.6.5.
  • If immediate upgrade is not possible, check OpenProject vendor guidance.
  • Review whether group membership names expose sensitive business context.
  • Limit “View Members” permission to users with a clear business need.

Validation and detection

  • Inventory OpenProject instances and record installed versions.
  • Confirm whether the deployment uses groups to manage users.
  • Review roles granting “View Members” permission across projects.
  • After upgrading, verify the installed version is 17.0.1 or 16.6.5 or later.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23721 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-23721Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
opfopenproject< 16.6.5, = 17.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.