# CVE-2019-10047: PyDio Stored XSS Vulnerability

> An authenticated attacker can execute arbitrary JavaScript in a victim's browser by uploading and sharing malicious HTML files via the file preview feature.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A: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:** 31 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5ghg-233h-7j79, PYSEC-2026-902

## What is CVE-2019-10047?

CVE-2019-10047 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 May 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored XSS vulnerability exists in the web application of Pydio through 8.2.2 that can be exploited by levering the file upload and file preview features of the application. An authenticated attacker can upload an HTML file containing JavaScript code and afterwards a file preview URL can be used to access the uploaded file. If a malicious user shares an uploaded HTML file containing JavaScript code with another user of the application, and tricks an authenticated victim into accessing a URL that results in the HTML code being interpreted by the web browser, then the included JavaScript code is executed under the context of the victim user session.

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

## Which versions are affected by CVE-2019-10047?

3 open source packages ship an affected version, including pydio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pydio` | PyPI | All versions to 8.2.2 | None |
| `pydio` | PyPI | All versions to 8.2.2 | None |
| `pydio` | PyPI | All versions to 8.2.2 | None |

Products: Pydio Pydio.

## How do I fix CVE-2019-10047?

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

## Is CVE-2019-10047 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4267](https://insights.sbomify.com/CVE-2013-4267/): Command injection in Ajaxeplorer (critical 9.8)
- [CVE-2019-9642](https://insights.sbomify.com/CVE-2019-9642/): Code injection in n/a (critical 9.8)
- [CVE-2018-20718](https://insights.sbomify.com/CVE-2018-20718/): Deserialization in n/a (critical 9.8)
- [CVE-2015-3431](https://insights.sbomify.com/CVE-2015-3431/): Command injection in n/a (critical 9.8)
- [CVE-2019-20452](https://insights.sbomify.com/CVE-2019-20452/): Deserialization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10047 and fix it if it is affected.

What it is: CVE-2019-10047 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 May 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10047 in the wild and no public exploit code.

Affected packages and fixed versions:
- pydio (PyPI): affected all versions up to 8.2.2; no fix listed
- pydio (PyPI): affected all versions up to 8.2.2; no fix listed
- pydio (PyPI): affected all versions up to 8.2.2; no fix listed

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-2019-10047/ (Markdown: https://insights.sbomify.com/CVE-2019-10047/index.md)
```

## Sources

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

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