# CVE-2022-48085: Cross-site scripting in n/a

> Attackers can inject malicious HTML into the Work Space Name parameter, potentially executing scripts in user sessions.

- **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:** 6 Feb 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-j9wr-m578-9wvj

## What is CVE-2022-48085?

CVE-2022-48085 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Softr v2.0 was discovered to contain a HTML injection vulnerability via the Work Space Name parameter.

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

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

It affects 1 product.


Products: Softr Softr.

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

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

## Is CVE-2022-48085 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-40434](https://insights.sbomify.com/CVE-2022-40434/): Cross-site scripting in n/a (critical 9.8)
- [CVE-2022-32407](https://insights.sbomify.com/CVE-2022-32407/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48085 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Feb 2023. 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-2022-48085 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-2022-48085/ (Markdown: https://insights.sbomify.com/CVE-2022-48085/index.md)
```

## Sources

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

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