Quick answers
- Is CVE-2026-96371 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96371 being exploited in the wild.
- How severe is CVE-2026-96371?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Drupal Webform <6.2.12, >=6.3.0 <6.3.1; Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform ECOSYSTEM:introduced=0,fixed=6.2.12|ECOSYSTEM:introduced=6.3.0,fixed=6.3.1.
- Is there a fix for CVE-2026-96371?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform: upgrade to 6.2.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96371 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96371?
- Check whether you run Drupal Webform or Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Packagist:Https://Packages.Drupal.Org/8 Drupal/Webform: upgrade to 6.2.12 or later
Technical details
This is a cross-site scripting (XSS) vulnerability in the Webform module's source configuration handling. When the Webform UI module is not enabled, insufficient access controls on raw webform source editing allow authenticated users with webform creation or editing permissions to enter unsanitized configuration that is rendered without proper escaping. An attacker requires webform creation or editing permissions on the Drupal site to exploit this vulnerability; affected versions are 6.2.x prior to 6.2.12 and 6.3.0 prior to 6.3.1.
Affected products
- Drupal Webform <6.2.12, >=6.3.0 <6.3.1
Identifiers
- CVE-2026-96371
- DRUPAL-CONTRIB-2026-166
Timeline
- 2026-09-23: disclosed