Page Manager
The module does not properly protect its administration pages from forged requests. Anyone without logging in could trick an administrator into turning a page on or off without their knowledge. They could change this setting but could not view any hidden information.
- Who could do thisAnyone visiting the site. No login needed.
- Does it apply to youA site is affected if the user interface part of the module is turned on and the targeted user has the access right to administer pages.
- Has it been used in attacksNo sign of it.
- How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.
Tell your developerUpdate Page Manager to 8.x-4.1.
For developers: what the fix changed
Adds `_csrf_token: 'TRUE'` to the `entity.page.enable` and `entity.page.disable` routes in `page_manager_ui.routing.yml` to protect them against cross-site request forgery.
Also in this release Added Drupal 12 compatibility, converted procedural hooks to object-oriented hooks using attributes, and fixed an issue with outdated tempstore page statuses.
page_manager.info.yml+1 −1page_manager.module+8 −16page_manager.services.yml+7 −19page_manager_ui/page_manager_ui.info.yml+1 −1page_manager_ui/page_manager_ui.module+13 −123page_manager_ui/page_manager_ui.post_update.php+7 −0page_manager_ui/page_manager_ui.routing.yml+2 −0 fixpage_manager_ui/page_manager_ui.services.yml+5 −0page_manager_ui/src/Controller/PageManagerController.php+7 −1page_manager_ui/src/Entity/PageListBuilder.php+2 −11page_manager_ui/src/Form/PageGeneralForm.php+3 −9page_manager_ui/src/Hook/PageManagerUiHooks.php+179 −0