OroCommerce vulnerable to XSS when adding class name to Selector Manager on pages that use GrapeJS editor
Priority LOW 38CWE-79Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-79.
Summary
# 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 - [https://github.com/artf/grapesjs/issues/4411](https://github.com/artf/grapesjs/issues/4411) # Patch Update GrapeJS dependency to >=[v0.19.5](https://github.com/artf/grapesjs/releases/tag/v0.19.5)
Why it matters now
Fix Fixed oro/commerce (Packagist): 5.0.4
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | oro/commerce (Packagist) | 5.0 to before 5.0.4 | 5.0.4 | Patch available | GHSA-6f85-3f8q-qc94 |
- oro/commerce (Packagist) Vendor— Affected 5.0 to before 5.0.4 Fixed in 5.0.4 Patch available GHSA-6f85-3f8q-qc94
Remediation
- Fix · GHSA-6f85-3f8q-qc94 oro/commerce (Packagist) Fixed in 5.0.4 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-6f85-3f8q-qc94
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences