CVE-2023-49573
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 that could allow an attacker to execute persistent XSS through /add_command_action in action_value. 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 XSS vulnerability in VX Search Enterprise v10.2.14 allows injection of malicious JavaScript through the action_value parameter of the /add_command_action endpoint. The injected payload persists on the system and executes when users 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 VX Search Enterprise versionOpen the VX Search Enterprise application and navigate to Help > About, or check the installation directory for version information. Alternatively, access the web interface and look for version details in the footer or login page.Affected if The installed version is exactly 10.2.14.
-
Verify web interface is accessibleAttempt to access the VX Search Enterprise web interface via HTTP/HTTPS on the configured port (typically 8080 or 8443). Confirm the login page or dashboard loads.Affected if The web interface is accessible and responds.
-
Confirm /add_command_action endpoint existsSend a request to the /add_command_action endpoint using the web interface or direct HTTP request. This endpoint is used for configuring command actions. Access the application's command action configuration area through the web UI.Affected if The endpoint responds and allows configuration of command actions.
-
Inspect stored action configurations for malicious scriptsIn the web interface, navigate to the command action configuration section where action_value parameters are stored. Examine the stored values for any suspicious JavaScript tags, event handlers (onload, onerror, onclick), or encoded payloads. Check the underlying database or configuration files if direct database access is available.Affected if Stored action_value entries contain JavaScript code, script tags, or suspicious encoded content that was not intentionally configured by an administrator.
You are affected if VX Search Enterprise version 10.2.14 is installed and the /add_command_action endpoint contains or can store unsanitized action_value parameters with malicious script content.
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 proper input validation and output encoding on the action_value parameter in /add_command_action to sanitize user-supplied content before storage and display.
- 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-49573 — 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-49573 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