Security readout for executives and security teams
Plain-English summary
CVE-2022-35500 is a medium-severity cross-site scripting issue reported in Amasty Blog 2.10.3 through the leave-comment functionality. A user with low privileges could submit content that may run in another user's browser if that user views it. Business risk is mainly session exposure, content manipulation, and trust damage.
Executive priority
Treat as a moderate web application risk. Prioritize remediation for public-facing sites with active comments or authenticated customer areas, but it is not currently supported as an emergency issue by KEV or active-exploitation evidence.
Technical view
The CVE maps to CWE-79 and has CVSS 3.1 score 5.4: network reachable, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact. The provided sources do not name a fixed release or vendor advisory.
Likely exposure
Likely exposure is limited to environments running Amasty Blog 2.10.3 with the leave-comment feature enabled. The CVE record's affected product fields are incomplete, so confirm product and version from local extension inventories rather than relying only on metadata.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. A public GitHub reference exists, which may increase researcher and attacker awareness, but the provided evidence does not support claiming exploitation in the wild.
Researcher notes
Key uncertainty is metadata quality: the CVE title and description identify Amasty Blog 2.10.3, while affected vendor/product/version fields are listed as n/a. Do not expand scope beyond confirmed deployments. Validate stored or reflected behavior safely without publishing payloads.
Mitigation direction
Check Amasty or vendor guidance for a fixed version and apply supported updates.
If unable to update, consider disabling or moderating blog comments temporarily.
Review comment rendering for proper output encoding and script filtering.
Remove or sanitize suspicious stored comments after confirming exposure.
Use CSP as defense in depth, not as the primary fix.
Validation and detection
Inventory sites for Amasty Blog and confirm whether version 2.10.3 is present.
Verify whether leave-comment functionality is enabled and reachable by low-privilege users.
Review stored comments for unexpected script-like or HTML event content.
Confirm remediation in staging with non-destructive XSS validation methods.
Document product/version evidence because CVE affected metadata is incomplete.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
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.