# CVE-2025-3737: Google Maps: Store Locator - Critical - Unsupported - SA-CONTRIB-2025-038

> The Drupal Google Maps Store Locator module is unsupported and vulnerable, requiring users to migrate to a supported alternative.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2025
- **Updated:** 17 Apr 2025
- **Also known as:** DRUPAL-CONTRIB-2025-038, GHSA-v3r6-268x-w57p

## What is CVE-2025-3737?

CVE-2025-3737 is a medium-severity vulnerability in Drupal Google Maps: Store Locator, published on 16 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in Drupal Google Maps: Store Locator.This issue affects Google Maps: Store Locator: *.*.

## Which versions are affected by CVE-2025-3737?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/gmap_store_locator` | Packagist:https://packages.drupal.org/8 | All versions | None |

Products: Google Maps\  Store Locator Project.

## How do I fix CVE-2025-3737?

No fix has been published for CVE-2025-3737 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3737 being exploited?

There is no known exploitation of CVE-2025-3737 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3737 and fix it if it is affected.

What it is: CVE-2025-3737 is a medium-severity vulnerability in Drupal Google Maps: Store Locator, published on 16 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3737 in the wild and no public exploit code.

Affected product: Drupal Google Maps: Store Locator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3737/ (Markdown: https://insights.sbomify.com/CVE-2025-3737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3737
- OSV: https://osv.dev/vulnerability/CVE-2025-3737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3737/
Summaries are generated and may contain mistakes; the official description above is the record.