SA-CONTRIB-2026-160: Critical severity drupal/webform vulnerability

Published Sep 23, 2026
·
Updated

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.

Credit

Brian Willows (hsjbrianwillows)

Affected Software

1 affected componentFixes available
drupal/webform<6.2.12, <6.3.1
6.2.126.3.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade drupal/webform to a version that resolves this vulnerability.

    Fixed in 6.2.12Fixed in 6.3.1

Event History

Sep 23, 2026
Advisory Published
via Drupal·12:00 AM
Data Sourced
via Drupal·12:00 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which sites are exposed to this issue?

A site is exposed only if it uses a Remote Post handler and renders that handler's response tokens in output. Sites that do not render Remote Post handler response tokens are not affected by the described attack path.

2

What must an attacker control to exploit it?

The attacker must be able to control or influence the response returned by a remote endpoint configured in a Remote Post handler. That response must then be rendered through handler response tokens.

3

What is the practical impact of successful exploitation?

Attacker-influenced response values can be rendered as HTML, resulting in cross-site scripting. The issue is therefore dependent on both the remote endpoint's response being influenceable and the relevant tokens being used in rendered output.

4

What can be done if patching is not immediately possible?

Avoid rendering Remote Post handler response tokens in output, and review configured remote endpoints to ensure untrusted parties cannot control or influence their responses.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203