# CVE-2020-36988: PDW File Browser <= v1.3 - Cross-Site Scripting (XSS)

> Authenticated attackers can inject malicious scripts via file rename or path parameters, executing arbitrary JavaScript in victims' browsers.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jan 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-qcgw-vvf3-5ppq

## What is CVE-2020-36988?

CVE-2020-36988 is a medium-severity cross-site scripting vulnerability in GuidoNeele PDW File Browser, published on 28 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

PDW File Browser version 1.3 contains stored and reflected cross-site scripting vulnerabilities that allow authenticated attackers to inject malicious scripts through file rename and path parameters. Attackers can craft malicious URLs or rename files with XSS payloads to execute arbitrary JavaScript in victims' browsers when they access the file browser.

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

## Which versions are affected by CVE-2020-36988?


## How do I fix CVE-2020-36988?

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

## Is CVE-2020-36988 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36988 and fix it if it is affected.

What it is: CVE-2020-36988 is a medium-severity cross-site scripting vulnerability in GuidoNeele PDW File Browser, published on 28 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36988 exists.

Affected product: GuidoNeele PDW File Browser. 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-2020-36988/ (Markdown: https://insights.sbomify.com/CVE-2020-36988/index.md)
```

## Sources

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

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