CVE-2023-49572
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stored (persistent) cross-site scripting vulnerability exists in VX Search Enterprise 10.2.14 and Disk Pulse Enterprise 10.4.18. The vulnerability is located in the /setup_odbc endpoint where the odbc_data_source, odbc_user, and odbc_password parameters accept unsanitized user input. An attacker can inject malicious JavaScript payloads that are stored on the server and executed in the browsers of users who subsequently load the affected page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.2.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Flexense productCheck Programs and Features (Windows) or list installed packages to confirm whether VX Search Enterprise or Disk Pulse Enterprise is installed. Look for the application in the system inventory.Affected if Either VX Search version 10.2.14 or Disk Pulse Enterprise version 10.4.18 is installed.
-
Check product version numberOpen the application GUI, or check the installed version via the program's About/Help menu, or locate the executable properties (right-click the .exe file and view Details).Affected if The installed version matches exactly 10.2.14 for VX Search or 10.4.18 for Disk Pulse Enterprise.
-
Verify /setup_odbc endpoint accessibilityAccess the application's web interface (if available) and navigate to or attempt to reach the /setup_odbc URL path. This is typically a configuration page for ODBC database connections.Affected if The endpoint responds and displays a form containing odbc_data_source, odbc_user, and odbc_password fields.
-
Inspect ODBC configuration storageExamine the application's configuration files or database where ODBC settings are stored. Look for entries in the odbc_data_source, odbc_user, and odbc_password fields.Affected if These fields contain unsanitized HTML, JavaScript, or script-related tags (such as <script>, event handlers like onload, onerror, or encoded variants).
A user is affected if they have VX Search Enterprise 10.2.14 or Disk Pulse Enterprise 10.4.18 installed AND the /setup_odbc configuration page is accessible with stored malicious payloads in the ODBC parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and output encoding for all user-supplied values in the /setup_odbc endpoint parameters. Alternatively, apply any available vendor patches for these products.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49572 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49572 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data