Summary
A high-severity improper authorization issue in RuoYi-Vue-Plus may allow a remote attacker to invoke workflow task operations without sufficient permission. Abuse of the affected task-completion and execution paths could result in arbitrary code execution, depending on deployment configuration and reachable functionality.
Affected context
The issue occurs in workflow task handling associated with FlwTaskController.java, FlwTaskServiceImpl.completeTask, CompleteExecuteComponent.process, and the Warm-Flow TaskService.skip and POST /workflow/task/completeTask paths. Risk is greatest when these interfaces are network-reachable and authorization checks do not adequately verify whether the requesting principal may perform the requested task operation.
Exploit preconditions
- Attack surface: Remotely reachable workflow task endpoints
- Required access: Access to the application interface; the exact authentication requirement depends on deployment configuration
- Trigger point: Task completion, task skipping, or related workflow execution processing
- Why exploitation is possible: Authorization enforcement may not sufficiently bind the requested operation to the caller's identity, role, tenant, or workflow permissions, potentially allowing execution of privileged processing paths
Why this happens
The underlying bug is an authorization failure in workflow task operations. CWE-863 applies when a system does not correctly verify whether a requester is permitted to perform a specific action on a specific resource. In this case, insufficient authorization checks around task completion or skipping may expose execution logic to callers who should not be able to invoke it; downstream behavior could then enable arbitrary code execution.
Potential impact
- An attacker may execute unauthorized workflow actions
- An attacker could trigger arbitrary code execution in the application process
- Sensitive application data may be exposed or modified
- Workflow state and business records could be altered
- The application environment may be used for further compromise or lateral movement
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every workflow action boundary rather than relying only on client-side controls or route-level authentication.
Common defensive patterns include:
- Applying server-side, deny-by-default authorization checks to task completion and skipping operations
- Binding permissions to the authenticated principal, task owner, tenant, workflow, and requested resource
- Rechecking authorization inside service-layer methods, not only in controllers
- Separating workflow data validation from execution-capable processing
- Restricting dangerous execution capabilities and running application processes with least privilege
- Using narrowly scoped roles and avoiding shared administrative credentials
- Recording and reviewing authorization failures and sensitive workflow actions
How teams detect issues like this
Organizations can assess this issue through:
- Static analysis for controller or service methods that perform state-changing actions without authorization annotations or policy checks
- Code review of task completion, skipping, and execution paths for missing object-level and tenant-level permission validation
- Integration tests that attempt workflow operations across users, roles, tenants, and unrelated tasks
- API gateway and application policies requiring authenticated, explicitly authorized access to workflow endpoints
- Runtime monitoring for unusual task-operation volume, cross-user task access, and unexpected process execution
- Automated security review tools that identify missing authorization checks and inconsistent enforcement between controller and service layers

