CVE-2018-18570 Planon before Live Build 41 has XSS.
Medium 6.1
Published
Updated
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)
- Exploited in the wild
- Not known
- Fix
- None listed
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
Which versions are affected by CVE-2018-18570?
It affects 1 product.
Products include 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: 1 Nuclei template.
Sources
Also known as GHSA-h8fj-8mr5-p56w.