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

> Cross-site scripting vulnerability in FusionDirectory allows attackers to inject malicious scripts via URL parameters, potentially leading to session hijacking or code execution.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Nov 2022
- **Updated:** 9 Jul 2026
- **Also known as:** DEBIAN-CVE-2022-36180, GHSA-f585-354r-gp9r, UBUNTU-CVE-2022-36180

## What is CVE-2022-36180?

CVE-2022-36180 is a critical cross-site scripting vulnerability in n/a, published on 22 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Fusiondirectory 1.3 is vulnerable to Cross Site Scripting (XSS) via /fusiondirectory/index.php?message=[injection], /fusiondirectory/index.php?message=invalidparameter&plug={Injection], /fusiondirectory/index.php?signout=1&message=[injection]&plug=106.

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

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

It affects 1 product.


Products: Fusiondirectory Fusiondirectory.

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

Upgrade to a fixed version.

## Is CVE-2022-36180 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36179](https://insights.sbomify.com/CVE-2022-36179/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36180 is a critical cross-site scripting vulnerability in n/a, published on 22 Nov 2022. An attacker can exploit it over the internet without logging in, 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-36180 exists.

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-36180/ (Markdown: https://insights.sbomify.com/CVE-2022-36180/index.md)
```

## Sources

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

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