Paragraphs Edit
The module does not properly check access rights on the edit and delete pages for a content block. Someone with an ordinary account could edit or delete blocks they should not have access to. They could read hidden data and change information on the site.
- Who could do thisOnly someone with a login on your site.
- Does it apply to youA site is affected if an attacker has an account on the site and knows or guesses the ID of the content block.
- 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 Paragraphs Edit to 3.0.2.
For developers: what the fix changed
The fix adds a custom access check to the edit, clone, and delete routes to verify that the paragraph belongs to the root parent specified in the path. This is implemented in src/Access/ParagraphLineageAccessCheck.php and applied via paragraphs_edit.routing.yml and paragraphs_edit.services.yml.
Also in this release The release also fixes a TypeError in the lineage inspector, improves revision handling, adds cancel links to forms, and refactors form preparation logic.
.gitlab-ci.yml+0 −1paragraphs_edit.module+32 −0paragraphs_edit.routing.yml+3 −0 fixparagraphs_edit.services.yml+5 −0 fixsrc/Access/ParagraphLineageAccessCheck.php+57 −0 fixsrc/Form/ParagraphCloneForm.php+7 −3src/Form/ParagraphDeleteForm.php+7 −0src/Form/ParagraphEditForm.php+26 −33src/ParagraphFormHelperTrait.php+24 −0src/ParagraphLineageInspector.php+1 −1src/ParagraphLineageRevisioner.php+2 −1