# CVE-2020-25069: USVN (aka User-friendly SVN) before 1.0.10 allows attackers to execute arbitrary code in the commit view.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gxc5-6328-23q6

## What is CVE-2020-25069?

CVE-2020-25069 is a critical vulnerability in n/a, published on 1 Sep 2020. 

### Official description

USVN (aka User-friendly SVN) before 1.0.10 allows attackers to execute arbitrary code in the commit view.

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

It affects 1 product.


Products: Usvn Usvn.

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

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

## Is CVE-2020-25069 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-17363](https://insights.sbomify.com/CVE-2020-17363/): Command injection in n/a (critical 9.9)
- [CVE-2020-25070](https://insights.sbomify.com/CVE-2020-25070/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-0695](https://insights.sbomify.com/CVE-2018-0695/): Cross-site scripting in User-friendly SVN (USVN) (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-25069 is a critical vulnerability in n/a, published on 1 Sep 2020. 
Exploitation: There is no known exploitation of CVE-2020-25069 in the wild and no public exploit code.

Affected product: n/a. 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-25069/ (Markdown: https://insights.sbomify.com/CVE-2020-25069/index.md)
```

## Sources

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

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