CVE-2025-66468 is a high-severity (CVSS 7.6) Cross-site Scripting (XSS) vulnerability in aimeos/ai-cms-grapesjs. O3 Security confirms whether CVE-2025-66468 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Aimeos GrapesJS CMS extension possible stores XSS exploitable by authenticated editors
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.8 |
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2022.04.1&&< 2022.10.9 | 2022.10.9 |
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2023.04.1&&< 2023.10.15 | 2023.10.15 |
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2024.04.1&&< 2024.10.8 | 2024.10.8 |
| 🐘Packagist | aimeos/ai-cms-grapesjs | ≥ 2025.04.1&&< 2025.10.2 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 CVE-2025-66468 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 pinpoints whether CVE-2025-66468 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-66468. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-66468 in your dependencies?
O3 detects CVE-2025-66468 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.