# CVE-2026-78394: Link Library < 7.9.6 - Contributor+ Path Traversal via 'filepath' Parameter

> Contributors can write image files outside the web root via path traversal, allowing arbitrary file overwrites within server permissions.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/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:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-qx4g-fv3v-h498

## What is CVE-2026-78394?

CVE-2026-78394 is a medium-severity path traversal vulnerability in Unknown Link Library, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Link Library WordPress plugin before 7.9.6 does not sanitize a user-supplied destination folder before writing a generated image to disk, allowing users with the Contributor role and above to create directories and write or overwrite image files anywhere the web server can write, including outside the site's document root.

The written file name is always numeric with a fixed image extension, so executable code cannot be planted this way.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-78394 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78394 is a medium-severity path traversal vulnerability in Unknown Link Library, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78394 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-78394/ (Markdown: https://insights.sbomify.com/CVE-2026-78394/index.md)
```

## Sources

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

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