# CVE-2026-73243: kkFileView: Unauthenticated SSRF via /addTask with fullfilename type-confusion bypass

> Unauthenticated attackers can trigger Server-Side Request Forgery via the /addTask endpoint by manipulating file type parameters, potentially accessing internal resources.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/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:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-gwwj-52hv-6g2m

## What is CVE-2026-73243?

CVE-2026-73243 is a medium-severity server-side request forgery vulnerability in kekingcn kkFileView, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

kkFileView is a universal file online preview project based on Spring Boot. Prior to 5.0.1, the unauthenticated GET /addTask endpoint in kkFileView is omitted from TrustHostFilter and TrustDirFilter in server/src/main/java/cn/keking/config/WebConfig.java, allowing FileConvertQueueTask to fetch an attacker-selected URL after FileHandlerService#getFileAttribute uses the fullfilename parameter to force an OFFICE, COMPRESS, or CAD type. This issue is fixed in version 5.0.1.

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

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


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

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

## Is CVE-2026-73243 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73243 is a medium-severity server-side request forgery vulnerability in kekingcn kkFileView, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73243 exists.

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

## Sources

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

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