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

> Cross-site scripting in RageFrame2 allows attackers to inject scripts via user agent parameters, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** No
- **Published:** 16 Aug 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-xmcr-4fjr-782r

## What is CVE-2022-36530?

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

An issue was discovered in rageframe2 2.6.37. There is a XSS vulnerability in the user agent related parameters of the info.php page.

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

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

It affects 1 product.


Products: Rageframe Rageframe.

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

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

## Is CVE-2022-36530 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-30878](https://insights.sbomify.com/CVE-2024-30878/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-30879](https://insights.sbomify.com/CVE-2024-30879/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-30880](https://insights.sbomify.com/CVE-2024-30880/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2024-30883](https://insights.sbomify.com/CVE-2024-30883/): Cross-site scripting in n/a (medium 4.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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