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

> An XSS vulnerability in Syncovery for Linux allows attackers to inject scripts, potentially leading to code execution or data theft.

- **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:** 16 Sep 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-2793-3243-f8xx

## What is CVE-2022-36533?

CVE-2022-36533 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 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

Super Flexible Software GmbH & Co. KG Syncovery 9 for Linux v9.47x and below was discovered to contain a cross-site scripting (XSS) vulnerability.

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

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

It affects 1 product.


Products: Syncovery Syncovery.

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

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

## Is CVE-2022-36533 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36536](https://insights.sbomify.com/CVE-2022-36536/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-36534](https://insights.sbomify.com/CVE-2022-36534/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36533 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 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: There is no known exploitation of CVE-2022-36533 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-36533/ (Markdown: https://insights.sbomify.com/CVE-2022-36533/index.md)
```

## Sources

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

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