The vulnerability stems from missing CSRF protections on split state modification routes. While no patch diffs are available, the security advisory explicitly states that routes for enabling/disabling splits lacked CSRF tokens. In Drupal's architecture, these operations would be handled by controller methods tied to routes in config_split.routing.yml. The controller methods 'enable' and 'disable' would be invoked during split state changes and would appear in runtime profiles when processing these requests. The high confidence comes from the direct mapping between the described vulnerability pattern (missing route-level CSRF protection) and Drupal's controller-based routing architecture.