Summary
Genealogy, a PHP-based family tree application, contains a critical broken access control flaw that allows any authenticated user to transfer ownership of arbitrary non-personal teams to themselves.
When exploited, this issue can lead to full takeover of other users' team workspaces and unrestricted access to all genealogy data associated with the compromised teams.
Affected context
The vulnerability occurs in the logic that manages team ownership and permissions for non-personal teams within the Genealogy application.
It manifests when the backend accepts ownership transfer requests without correctly enforcing authorization checks that ensure only legitimate team owners or appropriately privileged roles can perform this action.
Any environment where multiple users collaborate using shared or organizational teams, and where authenticated users can access team-related functionality, may be exposed if proper access control rules are not applied at the server side.
Exploit preconditions
- Attack surface: Web application interface (HTTP endpoints handling team ownership and membership management).
- Required access: Any authenticated user account; no elevated or administrative role is necessary.
- Trigger point: Sending a crafted request or using existing functionality that initiates a team ownership transfer for a non-personal team owned by another user.
- Why exploitation is possible: The server-side logic does not consistently verify that the requesting user is the current owner (or otherwise authorized) before approving ownership changes, resulting in missing authorization on a sensitive state-changing operation.
Why this happens
The issue stems from missing or insufficient authorization checks around a privileged operation: transferring ownership of non-personal teams.
Instead of deriving permissions on the server from the current authenticated user's role and relationship to the team, the application implicitly trusts that an authenticated request to perform ownership transfer is legitimate.
This aligns with CWE-862: Missing Authorization, where access control is either not enforced or is incorrectly assumed to have been handled elsewhere, allowing users to perform actions outside their intended permission scope.
Potential impact
- An authenticated user may take ownership of any non-personal team.
- Attackers could gain unrestricted access to all genealogy records, media, and metadata stored under compromised team workspaces.
- Malicious users can modify, delete, or falsify genealogy data associated with hijacked teams.
- Confidential family information and collaboration history can be exposed to unauthorized parties.
- Organizational or research groups relying on team-based separation may experience data integrity loss and trust erosion.
General mitigation guidance
Mitigation centers on enforcing strict server-side authorization for all ownership and permission changes:
- Require the application to verify that the requester is the current team owner or holds a specific privileged role before approving ownership transfers.
- Implement a robust access control model (e.g., role-based or attribute-based) that clearly defines who can manage team ownership, and centralize those checks in reusable middleware or service layers.
- Treat team identifiers and ownership-related parameters as untrusted input; derive effective permissions from the authenticated user session and server-side state, not from client-provided claims.
- Consider adding explicit confirmation flows for sensitive actions (such as ownership transfer), with clear auditing and optional out-of-band notifications to previous owners.
- Apply the principle of least privilege so that standard authenticated users do not have access to high-impact administrative actions by default.
How teams detect issues like this
Effective detection focuses on identifying missing or weak authorization around team and ownership operations:
- Use static analysis or manual code review to locate endpoints or controller actions that modify team ownership, membership, or permissions and verify that they consistently enforce server-side authorization checks.
- Look for patterns where ownership transfer or access changes are allowed based only on client-supplied identifiers (e.g., team ID, user ID) without verifying the caller's relationship to the resource.
- Review access control middleware or policy components to ensure they are actually invoked for all team-related routes and that they distinguish between personal and non-personal teams.
- Analyze audit logs for suspicious patterns, such as frequent team ownership transfers initiated by low-privilege accounts or large numbers of teams changing owners in a short timeframe.
- Integrate automated security testing into CI/CD (including authorization-focused tests) to validate that only authorized roles can perform team ownership changes.

