# CVE-2026-78397: Link Library < 7.9.6 - Unauthenticated SSRF via Reciprocal Link Validation

> Unauthenticated attackers can exploit SSRF in Link Library plugin to access internal network services and gather response data.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/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:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-6rpr-h6cv-7xm2

## What is CVE-2026-78397?

CVE-2026-78397 is a medium-severity server-side request forgery vulnerability in Unknown Link Library, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Link Library WordPress plugin before 7.9.6 does not validate the destination of a user-supplied URL before falling back to an unprotected fetch when its safe request is rejected, allowing unauthenticated visitors to make the site issue requests to hosts on its internal network and to learn from the response whether an internal service answered.

Versions below 7.8.8 are covered by CVE-2025-68600; this entry covers 7.8.8 through 7.9.5, where that fix was incomplete. Exploitation requires the site owner to have published the Link Library WordPress plugin before 7.9.6's public link submission form with reciprocal-link validation enabled.

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

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


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

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

## Is CVE-2026-78397 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78397 is a medium-severity server-side request forgery vulnerability in Unknown Link Library, published on 25 Sep 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-78397 in the wild and no public exploit code.

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

## Sources

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

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