# CVE-2026-39728: WordPress Instapage Plugin plugin <= 3.7.2 - Server Side Request Forgery (SSRF) vulnerability

> Unauthenticated attackers can exploit SSRF in the Instapage WordPress plugin to access internal resources or bypass security controls.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-f9x9-mxcq-hx6w

## What is CVE-2026-39728?

CVE-2026-39728 is a high-severity server-side request forgery vulnerability in instapagedev Instapage Plugin, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated Server Side Request Forgery (SSRF) in Instapage Plugin <= 3.7.2 versions.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-39728?


## How do I fix CVE-2026-39728?

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

## Is CVE-2026-39728 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39728 and fix it if it is affected.

What it is: CVE-2026-39728 is a high-severity server-side request forgery vulnerability in instapagedev Instapage Plugin, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-39728 in the wild and no public exploit code.

Affected product: instapagedev Instapage Plugin. 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-2026-39728/ (Markdown: https://insights.sbomify.com/CVE-2026-39728/index.md)
```

## Sources

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

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