LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10128: SearchBlox product before V-9.2.1 is vulnerable to Stored-Cross Site Scripting

SearchBlox product with version before 9.2.1 is vulnerable to stored cross-site scripting at multiple user input parameters. In SearchBlox products multiple parameters are not sanitized/validate properly which allows an attacker to inject malicious JavaScript.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

SearchBlox versions before 9.2.1 can store malicious JavaScript submitted through multiple input fields. If another user later views that stored content, the script may run in their browser. The sources do not provide a CVSS score, affected parameter names, or confirmed exploitation.

Executive priority

Treat this as a targeted remediation item for any SearchBlox deployment below 9.2.1. It is not documented as actively exploited in the supplied sources, but stored XSS can affect privileged sessions and should be addressed in normal vulnerability maintenance windows.

Technical view

CVE-2020-10128 is a CWE-79 stored cross-site scripting issue in SearchBlox before 9.2.1. The CVE states multiple user input parameters were not properly sanitized or validated, allowing JavaScript injection. Authentication requirements, exact parameters, and vendor-fixed code details are not included in the supplied sources.

Likely exposure

Organizations running SearchBlox below version 9.2.1 are the known exposed group. Risk is higher where untrusted or lower-privileged users can submit content that administrators or other users later view. The bundle does not identify hosted editions, modules, or exact vulnerable routes.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Stored XSS can be business-impacting because execution occurs in a victim user's browser context, but the sources do not confirm exploit maturity, required privileges, or real-world campaigns.

Researcher notes

Evidence is sparse. The CVE identifies stored XSS across multiple parameters but omits parameter names, privilege requirements, CVSS, and exploit references. Validation should focus on version exposure, reachable content-submission paths, and confirming vendor remediation rather than assuming broader affected products.

Mitigation direction

  • Inventory SearchBlox deployments and confirm exact installed versions.
  • Upgrade SearchBlox deployments below 9.2.1 according to vendor guidance.
  • If upgrade timing is constrained, check SearchBlox guidance for supported workarounds.
  • Review application access paths that allow untrusted content submission.
  • Monitor stored content and logs for suspicious script-like submissions.

Validation and detection

  • Confirm no production SearchBlox instance is below version 9.2.1.
  • Review the vendor 9.2.1 changelog against deployed versions.
  • Identify forms or fields accepting user-controlled content in SearchBlox.
  • Check whether lower-privileged users can submit content viewed by privileged users.
  • After remediation, verify stored content is safely rendered in a test environment.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10128 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SearchBloxSearchBlox0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.