GHSA-424m-fj2q-g7vg is a high-severity (CVSS 7.6) Cross-site Scripting (XSS) vulnerability in aimeos/ai-cms-grapesjs. A fix is available for aimeos/ai-cms-grapesjs — see the affected versions and patch details below.
Aimeos GrapesJS CMS extension has possible stored XSS that's exploitable by authenticated editors
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-424m-fj2q-g7vg.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-424m-fj2q-g7vg plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
aimeos/ai-cms-grapesjs🐘aimeos/ai-cms-grapesjs🐘aimeos/ai-cms-grapesjs🐘aimeos/ai-cms-grapesjs🐘aimeos/ai-cms-grapesjsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
The Aimeos GrapesJS CMS extension provides page editor for creating content pages based on extensible components. Prior to 2021.10.8, 2022.10.8, 2023.10.8, 2024.10.8, and 2025.10.8, Javascript code can be injected by malicious editors for a stored XSS attack if the standard Content Security Policy is disabled. This vulnerability is fixed in 2021.10.8, 2022.10.8, 2023.10.8, 2024.10.8, and 2025.10.8.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2021.04.1&&< 2021.10.8 | 2021.10.8composer require aimeos/ai-cms-grapesjs:^2021.10.8 |
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2022.04.1&&< 2022.10.9 | 2022.10.9composer require aimeos/ai-cms-grapesjs:^2022.10.9 |
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2023.04.1&&< 2023.10.15 | 2023.10.15composer require aimeos/ai-cms-grapesjs:^2023.10.15 |
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2024.04.1&&< 2024.10.8 | 2024.10.8composer require aimeos/ai-cms-grapesjs:^2024.10.8 |
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2025.04.1&&< 2025.10.2 | 2025.10.2composer require aimeos/ai-cms-grapesjs:^2025.10.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aimeos/ai-cms-grapesjs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aimeos/ai-cms-grapesjs to 2021.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-424m-fj2q-g7vg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-424m-fj2q-g7vg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-424m-fj2q-g7vg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-424m-fj2q-g7vg in your dependencies?
O3 Security finds GHSA-424m-fj2q-g7vg across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.