An authorization bypass allows authenticated users to perform unauthorized operations on workflow schedules, workflow definitions, and task instances across different projects. The system verifies permissions against the provided `projectCode` but does not confirm if the target resource actually belongs to that project. Consequently, a user with permissions in one project can use that project's code alongside a resource identifier from another project to bypass access restrictions. This allows attackers to alter workflow availability and interfere with task execution in unauthorized projects via the following endpoints:
- 'POST /projects/{projectCode}/schedules/{id}/online'
- 'POST /projects/{projectCode}/schedules/{id}/offline'
- 'POST /projects/{projectCode}/workflow-definition/{code}/release'