# CVE-2023-49572: XSS vulnerability in VX Search Enterprise

> Attackers can inject persistent JavaScript via ODBC parameters in VX Search and Disk Pulse Enterprise, potentially leading to session hijacking or malicious actions.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2024
- **Updated:** 21 May 2025

## What is CVE-2023-49572?

CVE-2023-49572 is a high-severity cross-site scripting vulnerability in Flexense Disk Pulse Enterprise, published on 24 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been discovered in VX Search Enterprise affecting version 10.2.14, and in Disk Pulse Enterprise 10.4.18 version, that could allow an attacker to execute persistent XSS through /setup_odbc in odbc_data_source, odbc_user and odbc_password parameters. This vulnerability could allow an attacker to store malicious JavaScript payloads on the system to be triggered when the page loads.

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

## Which versions are affected by CVE-2023-49572?

It affects 1 product.


Products: Flexense Vx Search.

## How do I fix CVE-2023-49572?

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

## Is CVE-2023-49572 being exploited?

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

## Other vulnerabilities in Flexense Disk Pulse Enterprise

- [CVE-2017-15220](https://insights.sbomify.com/CVE-2017-15220/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-15662](https://insights.sbomify.com/CVE-2017-15662/): Denial of service in n/a (high 7.5)
- [CVE-2023-49573](https://insights.sbomify.com/CVE-2023-49573/): XSS vulnerability in VX Search Enterprise (high 7.1)
- [CVE-2023-49574](https://insights.sbomify.com/CVE-2023-49574/): XSS vulnerability in VX Search Enterprise (high 7.1)
- [CVE-2023-49575](https://insights.sbomify.com/CVE-2023-49575/): XSS vulnerability in VX Search Enterprise (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49572 and fix it if it is affected.

What it is: CVE-2023-49572 is a high-severity cross-site scripting vulnerability in Flexense Disk Pulse Enterprise, published on 24 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-49572 in the wild and no public exploit code.

Affected product: Flexense Disk Pulse Enterprise. 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-2023-49572/ (Markdown: https://insights.sbomify.com/CVE-2023-49572/index.md)
```

## Sources

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

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