# CVE-2026-107273: Gophish 0.11.0 through 0.12.1 SSRF via POST /api/import/site

> Authenticated low-privileged users can exploit SSRF in Gophish to access internal network resources and enumerate hosts via the site import API.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-5724-58m3-c7r6

## What is CVE-2026-107273?

CVE-2026-107273 is a medium-severity server-side request forgery vulnerability in gophish, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gophish 0.11.0 through 0.12.1 contains a server-side request forgery vulnerability that allows authenticated low-privileged users to reach loopback and private hosts via POST /api/import/site. Attackers can submit internal URLs, which the default dialer deny list does not block, to read service responses and enumerate internal hosts and ports through error messages.

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

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


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

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

## Is CVE-2026-107273 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107273 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107273 is a medium-severity server-side request forgery vulnerability in gophish, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107273 exists.

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

## Sources

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

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