# CVE-2022-39301: sra-admin is vulnerable to storage cross-site scripting (XSS) via unrestricted file upload

> An attacker can upload malicious HTML files to steal user information via stored XSS in the profile picture upload feature.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L`)
- **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:** 19 Oct 2022
- **Updated:** 22 Apr 2025

## What is CVE-2022-39301?

CVE-2022-39301 is a high-severity cross-site scripting vulnerability in momofoolish sra-admin, published on 19 Oct 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

sra-admin is a background rights management system that separates the front and back end. sra-admin version 1.1.1 has a storage cross-site scripting (XSS) vulnerability. After logging into the sra-admin background, an attacker can upload an html page containing xss attack code in "Personal Center" - "Profile Picture Upload" allowing theft of the user's personal information. This issue has been patched in 1.1.2. There are no known workarounds.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Sra-Admin Project Sra-Admin.

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

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

## Is CVE-2022-39301 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39301 is a high-severity cross-site scripting vulnerability in momofoolish sra-admin, published on 19 Oct 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-39301 exists.

Affected product: momofoolish sra-admin. 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-39301/ (Markdown: https://insights.sbomify.com/CVE-2022-39301/index.md)
```

## Sources

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

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