The vulnerability allows authenticated users to bypass authorization checks when creating pages, files, or users. This is due to the improper handling of the blueprint parameter in the create methods of the Page, File, and User models. The analysis of the security patch (commit f12ed3efa7656d84eb0aed4b1c6915075188bd46) reveals that the vulnerability is fixed by explicitly unsetting the blueprint key from the properties array ($props) at the beginning of the create methods in the PageActions, FileActions, and UserActions traits. This prevents attackers from injecting a custom blueprint with elevated privileges (e.g., setting 'create' => true in the options). The vulnerable functions are the create methods within these traits, which are utilized by their respective CMS model classes (Page, File, User). Therefore, any runtime profile during exploitation would show calls to Kirby\Cms\Page::create, Kirby\Cms\File::create, or Kirby\Cms\User::create as the entry points for the vulnerable operation.