Security readout for executives and security teams
Plain-English summary
AmazCart CMS 3.4 has a reflected cross-site scripting flaw in search. If a user can be persuaded to view affected search output or history, attacker-controlled JavaScript may run in that user’s browser. This is typically a user-targeted web risk, not a direct server takeover.
Executive priority
Treat this as a moderate-priority web application issue. Prioritize internet-facing commerce sites and administrator-accessible search workflows, because successful exploitation could affect customer trust, session integrity, or privileged browser actions.
Technical view
CVE-2023-54349 is CWE-79 reflected XSS in Spondonit AmazCart CMS 3.4 search handling. The supplied CVSS 3.1 score is 6.1: network reachable, low complexity, no privileges, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.
Likely exposure
Exposure is likely limited to organizations running AmazCart CMS version 3.4, especially public storefronts where search results or search history are reachable by customers, staff, or administrators.
Exploitation context
A public ExploitDB reference exists, but the bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires user interaction, usually through a crafted search interaction or link that causes script execution in the victim’s browser context.
Researcher notes
The source bundle names AmazCart CMS 3.4 only. No affected CPEs, fixed version, vendor patch, or active exploitation evidence are provided. Public exploit availability raises validation priority, but user interaction remains a key limiting factor.
Mitigation direction
- Inventory AmazCart CMS deployments and confirm whether version 3.4 is present.
- Check Spondonit, CodeCanyon, and advisory sources for fixed versions or vendor guidance.
- Upgrade if the vendor provides a corrected release for this issue.
- Apply output encoding and input handling controls around search and search history rendering.
- Use WAF or routing controls to reduce exposure while awaiting vendor guidance.
Validation and detection
- Confirm affected systems run AmazCart CMS 3.4 before assigning remediation work.
- Review search result and search history rendering for unencoded user-controlled input.
- Check web logs for suspicious search activity and unusual user-targeted links.
- Verify remediation in an authorized test environment without using production users.
- Retest after upgrade or control changes to confirm script content is not executed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2023-54349 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-51219CVE reference, VulnCheck · exploit
- Official Product HomepageCVE reference, VulnCheck · product
- Product ReferenceCVE reference, VulnCheck · product
- VulnCheck Advisory: AmazCart CMS 3.4 Reflected Cross-Site Scripting via SearchCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.