# CVE-2026-78395: Link Library < 7.10.0 - Unauthenticated Link Submission Login Requirement Bypass


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-57vw-f9g4-3923

## What is CVE-2026-78395?

CVE-2026-78395 is a medium-severity vulnerability in Unknown Link Library, published on 29 Oct 2026. 

### Official description

The Link Library WordPress plugin before 7.10.0 does not re-check the selected library's own login requirement when processing its front-end link submission, allowing unauthenticated users to submit links to a library configured to require login by reusing a form token obtained from another library that does not.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-78395 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78395 is a medium-severity vulnerability in Unknown Link Library, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-78395 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-78395/ (Markdown: https://insights.sbomify.com/CVE-2026-78395/index.md)
```

## Sources

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

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