The vulnerability allows a user with limited permissions ('Manage Playbook Configurations') to change a playbook's team, an action that should require higher privileges ('Manage Playbook Members'). This is due to a missing authorization check in the playbook update logic. The analysis of the security patch commit e1d6ec2c94e695fb74e0c0c11c0d45e028bb96f3 reveals the exact location of the fix. The file server/app/permissions_service.go was modified to add a new check within the PlaybookModifyWithFixes function. This new code block explicitly verifies if the TeamID of the playbook is being changed. If it is, the function now checks if the user has the PlaybookManageMembers permission and if they have access to the destination team. Before this patch, this check was absent, making the PlaybookModifyWithFixes function the vulnerable component that would appear in a runtime profile during exploitation of this vulnerability via the PUT /plugins/playbooks/api/v0/playbooks/{PLAYBOOK_ID} API endpoint.