dbcve.org
Vx SearchApplication · Flexense

CVE-2023-49575

MEDIUM · 6.1 CVSS v3.1 Published 2024-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A vulnerability has been discovered in VX Search Enterprise affecting version 10.2.14, in Sync Breeze Enterprise Server 10.4.18 version, and in Disk Pulse Enterprise 10.4.18 version, that could allow an attacker to execute persistent XSS through /setup_smtp in smtp_server, smtp_user, smtp_password and smtp_email_address 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 · high confidence

Stored XSS vulnerability in the /setup_smtp endpoint of VX Search Enterprise 10.2.14, Sync Breeze Enterprise Server 10.4.18, and Disk Pulse Enterprise 10.4.18 allows injection of malicious JavaScript through smtp_server, smtp_user, smtp_password, and smtp_email_address parameters. The payload persists and executes when the affected page loads.

MitigationImplement proper input validation and output encoding for all SMTP configuration parameters to neutralize malicious script execution. The vendor should issue patches for all affected product versions.

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
Vx SearchApplication
Affected:= 10.2.14

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed product and version
    Check the software version of Flexense VX Search, Sync Breeze Enterprise Server, or Disk Pulse Enterprise installed in your environment. This is typically available in the application's About section, help menu, or Windows Programs and Features.
    Affected if The installed version is 10.2.14 for VX Search Enterprise, 10.4.18 for Sync Breeze Enterprise Server, or 10.4.18 for Disk Pulse Enterprise.
  2. Locate the /setup_smtp endpoint
    Access the application's web interface and navigate to the /setup_smtp endpoint, or check if the SMTP configuration page is accessible via the administrative interface.
    Affected if The /setup_smtp endpoint or SMTP configuration page is accessible without authentication or with low-privileged access.
  3. Examine SMTP configuration storage
    Review the application's configuration files or database where SMTP settings (smtp_server, smtp_user, smtp_password, smtp_email_address) are stored. These values are typically saved in application config files or a local database.
    Affected if SMTP configuration parameters can be modified and are stored persistently by the application.
  4. Check for existing XSS payloads in SMTP fields
    Inspect the current values stored for smtp_server, smtp_user, smtp_password, and smtp_email_address parameters in the SMTP configuration. Look for script tags, event handlers, or other JavaScript injection patterns.
    Affected if Any of the SMTP parameters contain unsanitized HTML or JavaScript characters such as <script>, javascript:, onerror, onload, or similar XSS vectors.
  5. Verify XSS execution on page load
    Load the /setup_smtp page or the page that displays SMTP configuration and observe whether embedded JavaScript in the parameter values executes in the browser.
    Affected if JavaScript injected into SMTP parameters executes when viewing the configuration page, indicating stored XSS vulnerability.

You are affected if you are running VX Search Enterprise 10.2.14, Sync Breeze Enterprise Server 10.4.18, or Disk Pulse Enterprise 10.4.18 AND the /setup_smtp endpoint stores SMTP parameters without proper input validation, allowing stored JavaScript to execute when the configuration page loads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for all SMTP configuration parameters to neutralize malicious script execution. The vendor should issue patches for all affected product versions.

Fix this in Vx Search Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49575 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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