# CVE-2022-47412: ONLYOFFICE Workspace Search Stored XSS

> An attacker can inject malicious scripts via documents in ONLYOFFICE Workspace, potentially executing code or hijacking 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:** 7 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-2chf-w4v5-vmmg

## What is CVE-2022-47412?

CVE-2022-47412 is a medium-severity cross-site scripting vulnerability in ONLYOFFICE Workspace, published on 7 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

Given a malicious document provided by an attacker, the ONLYOFFICE Workspace DMS is vulnerable to a stored (persistent, or "Type II") cross-site scripting (XSS) condition.

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

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

It affects 1 product.


Products: Onlyoffice Workspace.

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

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

## Is CVE-2022-47412 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47412 is a medium-severity cross-site scripting vulnerability in ONLYOFFICE Workspace, published on 7 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47412 exists.

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

## Sources

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

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