Summary
Pterodactyl Panel contains an authorization flaw in scheduled task creation that allows a subuser with only schedule.update permission to run actions outside that permission's intended scope. By creating and triggering a scheduled task, an attacker may execute console commands, change server power state, or create backups.
Affected context
The issue occurs in Pterodactyl Panel deployments where subusers can create scheduled tasks and the application does not verify permissions for each action performed by those tasks. Risk is present when a subuser has schedule.update access but lacks the separate permissions associated with console commands, power operations, or backup creation.
Exploit preconditions
- Attack surface: Scheduled task management in the Pterodactyl Panel
- Required access: An authenticated subuser account with
schedule.updatepermission - Trigger point: Creation and immediate execution of a scheduled task
- Why exploitation is possible: Authorization is checked for task modification but not consistently re-evaluated for each privileged action executed by the task
Why this happens
The underlying bug is an authorization design failure in which permission checks are applied to the scheduled-task management operation but not to the individual actions that the task can invoke. This permits a user authorized to update schedules to reach operations requiring additional privileges, matching CWE-862, Missing Authorization.
Potential impact
- An attacker may execute unauthorized game-server console commands.
- An attacker could change the server's power state.
- An attacker may create backups without the intended authorization.
- Server data or gameplay state could be altered.
- The affected server could become unavailable or operationally disrupted.
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every privileged
action boundary rather than relying on permission checks for the parent
workflow alone.
Common defensive patterns include:
- Checking the caller's effective permissions for each scheduled-task action.
- Applying deny-by-default authorization for console, power, and backup operations.
- Separating schedule-management privileges from the privileges executed by task actions.
- Revalidating identity, scope, and authorization when a task is created and when it runs.
- Using least-privilege roles and minimizing subuser access to scheduling features.
- Recording and reviewing scheduled-task creation, modification, and execution events.
How teams detect issues like this
Organizations can identify similar weaknesses through:
- Static analysis and authorization testing for action handlers reachable through task schedulers.
- Code review checks confirming permission enforcement at each privileged operation.
- Policy tests that verify users cannot invoke console, power, or backup actions through indirect workflows.
- Integration tests covering combinations of subuser roles and scheduled-task actions.
- Audit-log monitoring for unexpected task creation, immediate execution, or privileged actions by low-privilege accounts.
Automated application-security review tools may help flag authorization checks that exist only at a workflow entry point.

