- Package
- drupal/webform
- Fixed in
- 6.2.12, 6.3.1
- Published
- Wed 23 Sep 2026, 17:14 LisbonUpdated Mon 26 Oct 2026, 03:25 Lisbon
In plain words
Webform Entity Print does not sufficiently restrict access to its print templates, allowing cross-site scripting (XSS) through its settings. The submodule must be enabled, and the attacker must have both the create webform and edit own webform permissions.
Am I affected?
Look for drupal/webform and its installed version in composer.lock. The advisory lists fixes in 6.2.12 and 6.3.1, but gives no affected version ranges. Check whether Webform Entity Print is enabled and whether any user role has both create webform and edit own webform permissions.
What to do
Check which version you have, then update to a fixed release for your branch (6.2.12, 6.3.1):
composer show drupal/webform | grep versions
composer update drupal/webform
If your version constraint in composer.json keeps you below a fixed release, raise it first. Whether your configuration is affected, and the exact version ranges, are in the advisory itself.
If you cannot update yet
The advisory says the vulnerability is mitigated by requiring both the create webform and edit own webform permissions, as well as the Webform Entity Print module being enabled.
The advisory's description
The Webform module allows site builders to create forms, collect submissions, and configure access to forms and submission data.
Webform includes a submodule called Webform Entity Print. This submodule doesn't sufficiently limit access to its print templates. When the submodule is enabled, a user with permissions to create a webform can exploit cross-site scripting (XSS) in submodule settings.
This vulnerability is mitigated by the fact that an attacker must have a role with create webform and edit own webform permissions, and the Webform Entity Print module must be enabled.
The advisory
- OSV.dev: DRUPAL-CONTRIB-2026-161
- The week's digest, with the other advisories from 21 Sep 2026
- All advisories for drupal/webform