# CVE-2020-9036: Jeedom through 4.0.38 allows XSS.


- **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
- **Fix available:** No
- **Published:** 5 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fq6m-28xv-2hw5

## What is CVE-2020-9036?

CVE-2020-9036 is a medium-severity vulnerability in n/a, published on 5 Aug 2020. 

### Official description

Jeedom through 4.0.38 allows XSS.

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

## Which versions are affected by CVE-2020-9036?

It affects 1 product.


Products: Jeedom Jeedom.

## How do I fix CVE-2020-9036?

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

## Is CVE-2020-9036 being exploited?

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

Public exploit code:

- Jeedom <=4.0.38 - Cross-Site Scripting (nuclei): http/cves/2020/CVE-2020-9036.yaml

## Other vulnerabilities in n/a

- [CVE-2021-42557](https://insights.sbomify.com/CVE-2021-42557/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9036 and fix it if it is affected.

What it is: CVE-2020-9036 is a medium-severity vulnerability in n/a, published on 5 Aug 2020. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-9036 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-2020-9036/ (Markdown: https://insights.sbomify.com/CVE-2020-9036/index.md)
```

## Sources

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

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