# CVE-2019-18207: Cross-site scripting in n/a

> An authenticated user can inject client-side code via the Title field, triggering execution when others view reports.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3c96-cx8m-c77h

## What is CVE-2019-18207?

CVE-2019-18207 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Oct 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In Zucchetti InfoBusiness before and including 4.4.1, an authenticated user can inject client-side code due to improper validation of the Title field in the InfoBusiness Web Component. The payload will be triggered every time a user browses the reports page.

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

## Which versions are affected by CVE-2019-18207?

It affects 1 product.


Products: Zucchetti Infobusiness.

## How do I fix CVE-2019-18207?

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

## Is CVE-2019-18207 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18204](https://insights.sbomify.com/CVE-2019-18204/): File upload in n/a (high 8.8)
- [CVE-2019-18206](https://insights.sbomify.com/CVE-2019-18206/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-18205](https://insights.sbomify.com/CVE-2019-18205/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18207 and fix it if it is affected.

What it is: CVE-2019-18207 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Oct 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-18207 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-2019-18207/ (Markdown: https://insights.sbomify.com/CVE-2019-18207/index.md)
```

## Sources

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

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