- Package
- drupal/leaflet
- Fixed in
- 10.4.13
- Published
- Wed 7 Oct 2026, 17:28 LisbonUpdated Mon 26 Oct 2026, 04:26 Lisbon
In plain words
An attacker could store a malicious script in a content title that runs when the Leaflet field formatter builds a map without filtering that title. The attacker must have permission to create or edit content used in a Leaflet map.
Am I affected?
Look for drupal/leaflet and its version in composer.lock. The advisory lists 10.4.13 as fixed but gives no affected version range. Check whether you use the Leaflet field formatter to build maps from content, and who has permission to create or edit that content.
What to do
Check which version you have, then update to a fixed release for your branch (10.4.13):
composer show drupal/leaflet | grep versions
composer update drupal/leaflet
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 vulnerability is mitigated by the requirement that an attacker have permission to create or edit content used in a Leaflet map.
The advisory's description
The Leaflet module provides integration with the Leaflet JS mapping library.
Under certain circumstances, when the Leaflet field formatter builds a map it does not filter content titles, leading to a stored cross-site scripting vulnerability.
This vulnerability is mitigated by the fact an attacker needs to have permission to create or edit content that is used in a Leaflet map.
The advisory
- OSV.dev: DRUPAL-CONTRIB-2026-204
- The week's digest, with the other advisories from 5 Oct 2026
- All advisories for drupal/leaflet