Skip to content

XSS vulnerability when add class name to Selector Manager on pages that uses GrapeJS editor

Moderate
rgrebenchuk published GHSA-6f85-3f8q-qc94 Jul 14, 2022

Package

composer oro/commerce (Composer)

Affected versions

>=5.0,<5.0.4

Patched versions

5.0.4

Description

Impact

Due to insufficient class name validation in GrapeJS library it's possible to add executable JS code in class name through Selector Manager

Relates to

Patch

Update GrapeJS dependency to >=v0.19.5

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:L/A:N

CVE ID

No known CVE

Weaknesses

No CWEs