# CVE-2022-39207: Persistent XSS in OneDev

> Persistent XSS in OneDev allows attackers to steal sessions and potentially execute arbitrary code on the server by targeting admins.

- **Severity:** Medium 5.4 (`CVSS:3.1/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:** 13 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-27fw-gv88-qrpg

## What is CVE-2022-39207?

CVE-2022-39207 is a medium-severity cross-site scripting vulnerability in theonedev onedev, published on 13 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Onedev is an open source, self-hosted Git Server with CI/CD and Kanban. During CI/CD builds, it is possible to save build artifacts for later retrieval. They can be accessed through OneDev's web UI after the successful run of a build. These artifact files are served by the webserver in the same context as the UI without any further restrictions. This leads to Cross-Site Scripting (XSS) when a user creates a build artifact that contains HTML. When accessing the artifact, the content is rendered by the browser, including any JavaScript that it contains. Since all cookies (except for the rememberMe one) do not set the HttpOnly flag, an attacker could steal the session of a victim and use it to impersonate them. To exploit this issue, attackers need to be able to modify the content of artifacts, which usually means they need to be able to modify a project's build spec. The exploitation requires the victim to click on an attacker's link. It can be used to elevate privileges by targeting admins of a OneDev instance. In the worst case, this can lead to arbitrary code execution on the server, because admins can create Server Shell Executors and use them to run any command on the server. This issue has been patched in version 7.3.0. Users are advised to upgrade. There are no known workarounds for this issue.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-39207?

It affects 1 product.


Products: Onedev Project Onedev.

## How do I fix CVE-2022-39207?

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

## Is CVE-2022-39207 being exploited?

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

## Other vulnerabilities in theonedev onedev

- [CVE-2021-21242](https://insights.sbomify.com/CVE-2021-21242/): Pre-Auth Unsafe Deserialization on AttachmentUploadServet (critical 10.0)
- [CVE-2021-21243](https://insights.sbomify.com/CVE-2021-21243/): Pre-Auth Unsafe Deserialization on KubernetesResource (critical 10.0)
- [CVE-2021-21244](https://insights.sbomify.com/CVE-2021-21244/): Pre-Auth SSTI via Bean validation message tampering (critical 10.0)
- [CVE-2021-21245](https://insights.sbomify.com/CVE-2021-21245/): Pre-Auth Arbitrary File Upload (critical 10.0)
- [CVE-2022-39206](https://insights.sbomify.com/CVE-2022-39206/): CI/CD Docker Escape in OneDev (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39207 and fix it if it is affected.

What it is: CVE-2022-39207 is a medium-severity cross-site scripting vulnerability in theonedev onedev, published on 13 Sep 2022. 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-2022-39207 exists.

Affected product: theonedev onedev. 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-2022-39207/ (Markdown: https://insights.sbomify.com/CVE-2022-39207/index.md)
```

## Sources

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

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