# CVE-2025-3739: Drupal 8 Google Optimize Hide Page - Critical - Unsupported - SA-CONTRIB-2025-040

> Critical vulnerability in an unsupported Drupal 8 module requires immediate removal or replacement due to lack of security patches.

- **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:** 16 Apr 2025
- **Also known as:** DRUPAL-CONTRIB-2025-040, GHSA-9799-8fpv-535m

## What is CVE-2025-3739?

CVE-2025-3739 is a medium-severity vulnerability in Drupal 8 Google Optimize Hide Page, published on 16 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in Drupal Drupal 8 Google Optimize Hide Page.This issue affects Drupal 8 Google Optimize Hide Page: *.*.

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

It affects 1 product.


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

Products: Drupal 8 Google Optimize Hide Page Project Drupal 8 Google Optimize Hide Page.

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

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

## Is CVE-2025-3739 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3739 is a medium-severity vulnerability in Drupal 8 Google Optimize Hide Page, 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-3739 in the wild and no public exploit code.

Affected product: Drupal 8 Google Optimize Hide Page. 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-3739/ (Markdown: https://insights.sbomify.com/CVE-2025-3739/index.md)
```

## Sources

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

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