Ricochet has been an invaluable partner in the development of our Drupal sites. Working with Casey, he lent a critical eye to our requirements to understand the feature set and objectives. During development, he was able to propose alternative implementations or creative solutions which met the requirements in an elegant and efficient manner. All the while, Casey maintained perspective on the user experience, to ensure that the product was not only bug free, but also easy to use an navigate. Furthermore, I could rely on Casey to keep me informed of issues and status with timely updates.
—Casey C., Future US

Geolocation Field - Critical - SQL Injection - SA-CONTRIB-2026-062

Wed, 2026-06-24 11:46 — Anonymous (not verified)

Project: Geolocation FieldDate: 2026-June-24Security risk: Critical 19 ∕ 25 AC:Basic/A:None/CI:All/II:All/E:Theoretical/TD:DefaultVulnerability: SQL InjectionAffected versions: <3.15.0CVE IDs: CVE-2026-13242Description: Geolocation modules adds a field to store coordinates and provides supporting plumbing for views and other modules.
One of the provided views filters does not sufficiently sanitize values if exposed to user input resulting in a SQL injection vulnerability.
This vulnerability is mitigated by the fact that a view must exist, that uses the aforementioned filter and it is set to accept user input.Solution: Install the latest version:

If you use the Geolocation Field module for Drupal, upgrade to Geolocation Field 8.x-3.15

Reported By:

Michael Maturi (michaelmaturi)

Fixed By:

Coordinated By:

cilefen (cilefen) of the Drupal Security Team
Neil Drumm (drumm) of the Drupal Security Team
Greg Knaddison (greggles) of the Drupal Security Team
Drew Webber (mcdruid) of the Drupal Security Team
Juraj Nemec (poker10) of the Drupal Security Team

Path to article https://www.drupal.org/sa-contrib-2026-062

Search form

Geolocation Field - Critical - SQL Injection - SA-CONTRIB-2026-062