Signature pad widget
The module does not properly clean user submitted content before saving it. Someone could upload a malicious file to run unsafe scripts and change or add data. They could not do this without the ability to submit a signature.
- 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 critical. Cyber Essentials expects a fix within 14 days. Do it this week.
Tell your developerUpdate Signature pad widget to 8.x-1.15.
For developers: what the fix changed
The fix introduces SVG sanitisation using the `enshrined/svg-sanitize` library in `SignWidgetController::save` and adds image validation to ensure uploaded files are valid PNGs in `SendSignForm::saveSign` and `SignWidget::massageFormValues`.
Also in this release The release also adds a new permission, implements CSRF token protection for AJAX requests, and refactors hook implementations to use attributes.
README.md+1 −1composer.json+3 −0 fixjs/build/signature.js+1 −1js/ckeditor5_plugins/signature/src/InsertSignatureCommand.js+10 −5js/sign_widget.js+17 −11sign_widget.module+6 −28sign_widget.permissions.yml+3 −0sign_widget.routing.yml+5 −2sign_widget.services.yml+5 −0src/Controller/SignWidgetController.php+70 −3 fixsrc/Form/SendSignForm.php+46 −7 fixsrc/Hook/SignWidgetHooks.php+56 −0