# CVE-2018-18570: Planon before Live Build 41 has XSS.


- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 29 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h8fj-8mr5-p56w

## What is CVE-2018-18570?

CVE-2018-18570 is a medium-severity vulnerability in n/a, published on 29 Jul 2019. 

### Official description

Planon before Live Build 41 has XSS.

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

## Which versions are affected by CVE-2018-18570?

It affects 1 product.


Products: Planonsoftware Planon.

## How do I fix CVE-2018-18570?

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

## Is CVE-2018-18570 being exploited?

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

Public exploit code:

- Planon <Live Build 41 - Cross-Site Scripting (nuclei): http/cves/2018/CVE-2018-18570.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18570 and fix it if it is affected.

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

## Sources

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

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