# CVE-2022-39240: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in MyGraph


- **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
- **Fix available:** No
- **Published:** 24 Sep 2022
- **Updated:** 25 Apr 2025

## What is CVE-2022-39240?

CVE-2022-39240 is a medium-severity vulnerability in renlm MyGraph, published on 24 Sep 2022. 

### Official description

MyGraph is a permission management system. Versions prior to 1.0.4 are vulnerable to a storage XSS vulnerability leading to Remote Code Execution. This issue is patched in version 1.0.4. There is no known workaround.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Mygraph Project Mygraph.

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

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

## Is CVE-2022-39240 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39240 is a medium-severity vulnerability in renlm MyGraph, published on 24 Sep 2022. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39240 exists.

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

## Sources

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

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