The Webform module allows site builders to create forms, collect submissions, and configure access to forms and submission data. Site builders may also configur...

Webform does not sufficiently filter Remote Post handler response values before displaying them through handler response tokens. If a site uses these tokens in rendered output, an attacker who can control or influence a configured remote endpoint's response could cause cross-site scripting by having returned values rendered as HTML.

Find drupal/webform and its version in composer.lock. The advisory lists fixes in 6.2.12 and 6.3.1, but gives no affected version range. Check whether your site uses Remote Post handler response tokens in rendered output, and whether an attacker could control or influence responses from a configured remote endpoint.

The advisory notes that exploitation requires both attacker control or influence over a configured remote endpoint's response and use of Remote Post handler response tokens in rendered output.

The Webform module allows site builders to create forms, collect submissions, and configure access to forms and submission data. Site builders may also configure handlers for processing submissions. Remote Post Handlers send webform data to other servers via APIs.

The module does not sufficiently filter response values from the Remote Post handler before those values are rendered through handler response tokens. If a site uses Remote Post handler response tokens in rendered output, values returned by a configured remote endpoint could be rendered as HTML, resulting in a cross-site scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must be able to control or influence the response from a configured remote endpoint, and the site must use Remote Post handler response tokens in rendered output.