LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35501: Stored Cross-site Scripting (XSS) exists in the Amasty Blog Pro 2.10.3 and 2.10.4 plugin for Magento 2 beca...

Stored Cross-site Scripting (XSS) exists in the Amasty Blog Pro 2.10.3 and 2.10.4 plugin for Magento 2 because of the duplicate post function.

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE is a stored cross-site scripting issue in Amasty Blog Pro for Magento 2 versions 2.10.3 and 2.10.4. A user with some authenticated access could store malicious content through the duplicate post function, potentially affecting another user who later views it.

Executive priority

Treat this as a moderate-priority web application issue. It is not confirmed as actively exploited, but commerce sites should remediate because stored XSS can affect customer trust, administrator sessions, and content integrity.

Technical view

CVE-2022-35501 is CWE-79 stored XSS with CVSS 3.1 score 5.4: network reachable, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, and no availability impact.

Likely exposure

Exposure appears limited to Magento 2 environments running Amasty Blog Pro 2.10.3 or 2.10.4. The provided CVE affected-product fields are sparse, so inventory confirmation is important.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. A public GitHub reference exists, but the provided evidence does not establish exploitation in the wild.

Researcher notes

The public record identifies the duplicate post function as the vulnerable area, but the bundle does not include patch details, precise privilege model, or exploit telemetry. Avoid assuming broader Amasty or Magento impact beyond the named versions.

Mitigation direction

  • Inventory Magento 2 sites for Amasty Blog Pro 2.10.3 or 2.10.4.
  • Check Amasty vendor guidance for a fixed version or supported workaround.
  • Restrict blog post creation and duplication permissions to trusted users.
  • Review existing duplicated blog posts for unexpected active content.
  • Prioritize remediation on externally administered or multi-user commerce sites.

Validation and detection

  • Confirm installed Amasty Blog Pro versions across Magento 2 environments.
  • Identify users or roles allowed to duplicate blog posts.
  • Review application logs for unusual blog post duplication activity.
  • Inspect blog content for unexpected embedded script-like markup.
  • Verify remediation against Amasty guidance after applying updates or workarounds.
Prepared
Confidence
medium
Sources
3

Public sources used

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-2022-35501 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
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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.

1CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-35501Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-79

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