LocalGov Workflows
A visitor could see a list of service contacts and the content assigned to them. They could view this private information but they could not change any data. They could not take full control of the website.
- Who could do thisAnyone visiting the site. No login needed.
- Does it apply to youAny site using this module.
- 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 LocalGov Workflows to 1.6.0.
For developers: what the fix changed
The fix updates the access permission for the localgov_content_by_owner view from access content to administer localgov_service_contact in the view configuration file and via an update hook in localgov_workflows_notifications.install.
modules/localgov_workflows_notifications/config/optional/views.view.localgov_content_by_owner.yml+1 −1 fixmodules/localgov_workflows_notifications/localgov_workflows_notifications.install+15 −0 fix