Sellacious eCommerce 4.6 contains a persistent cross-site scripting vulnerability in the Manage Your Addresses module that allows attackers to inject malicious scripts. Attackers can exploit multiple address input fields like full name, company, and address to execute persistent script code that can hijack user sessions and manipulate application modules.
Security readout for executives and security teams
Plain-English summary
CVE-2020-37003 is a stored cross-site scripting issue in Sellacious eCommerce 4.6. A logged-in attacker can save malicious script content in address fields. When later rendered, that script may affect other users, enabling session theft or unauthorized module manipulation.
Executive priority
Prioritize remediation for public e-commerce sites because stored XSS can affect customers and administrators. This is not rated critical, but it can undermine account trust and session security if exposed address fields are widely used.
Technical view
The issue is CWE-79 in the Manage Your Addresses module. Multiple address inputs, including full name, company, and address fields, can persist script content. CVSS 3.1 is 6.4: network reachable, low complexity, low privileges, no user interaction, changed scope, low confidentiality and integrity impact.
Likely exposure
Exposure is most likely on internet-facing Sellacious eCommerce 4.6 deployments that allow user account creation or address management by authenticated users. The provided affected-version data is inconsistent, listing version 0 while the title and description identify 4.6.
Exploitation context
The sources include a public ExploitDB reference, so proof-of-concept information exists. The bundle does not identify CISA KEV listing or active exploitation. Treat this as publicly documented but not confirmed as exploited in the wild from the provided evidence.
Researcher notes
Evidence supports stored XSS requiring low privileges. No official fixed version or mitigation is named in the provided bundle. The affected-version metadata conflicts with the narrative, so confirm product version directly during triage.
Mitigation direction
Check Sellacious vendor guidance for a fixed version or official workaround.
Upgrade only to a vendor-confirmed fixed release when available.
Review and sanitize stored address records for script-like content.
Restrict address-management access where business workflows allow.
Ensure server-side validation and contextual output encoding on address fields.
Validation and detection
Inventory Sellacious eCommerce deployments and confirm whether version 4.6 is present.
Identify public storefronts that allow authenticated address management.
Review address records for unexpected script content or encoded script fragments.
Check logs for suspicious address updates from low-privileged users.
Validate in staging that address fields render as text, not executable script.
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.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.