# CVE-2026-120428: PandaWiki 3.65.0 through 3.87.5 Stored XSS via /static-file/ PDF Query-String Bypass


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-7h72-q9rr-77j7

## What is CVE-2026-120428?

CVE-2026-120428 is a medium-severity vulnerability in Chaitin PandaWiki, published on 2 Nov 2026. 

### Official description

PandaWiki 3.65.0 through 3.87.5 contains a stored cross-site scripting vulnerability that allows unauthenticated attackers to upload HTML files with image extensions via /share/v1/common/file/upload. Attackers can lure administrators to /static-file/<key>?a=.pdf, bypassing the nginx attachment header to serve HTML inline and steal the panda_wiki_token JWT for session takeover.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-120428 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120428 is a medium-severity vulnerability in Chaitin PandaWiki, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120428 exists.

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

## Sources

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

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