Crucially, this swap occurs after the Symfony security firewall has already evaluated access_control against the primary dashboard URL. Because the provided routeName is not re-validated against path-based firewall rules, an attacker can access restricted routes that rely solely on security.yaml definitions for protection. This bypass is limited to path-based access controls; routes that utilize controller-level authorization such as #[IsGranted] or denyAccessUnlessGranted() are not affected, as those checks are re-evaluated against the new controller. The vulnerability allows unauthorized users to interact with sensitive administrative functionality if they can identify the target route name.

Impact

The vulnerability allows low-privileged users to access sensitive administrative routes protected only by path-based firewall configurations. If an application's security architecture relies on access_control rules to segment backend capabilities, an attacker can bypass these restrictions to gain unauthorized access to data or perform administrative functions. Routes that do not explicitly implement controller-level security checks are at high risk of exposure.

Recommendation

• Upgrade EasyAdminBundle to version 4.29.16 or 5.5.1 immediately to incorporate the required re-evaluation of access_control rules during custom-action dispatch.
• Audit all sensitive routes to ensure they implement controller-level security using #[IsGranted] or denyAccessUnlessGranted() as a secondary defense-in-depth measure.
• Monitor web application logs for unexpected access to admin-related controller paths that are typically hidden from low-privileged users.