Skip to content
Fencer Intel
high 7.7

CVE-2025-66468 json

Aimeos GrapesJS CMS extension possible stores XSS exploitable by authenticated editors

published 11mo ago modified 22d ago also GHSA-424m-fj2q-g7vg , EUVD-2025-200307

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist aimeos/ai-cms-grapesjs 2021.10.8, 2022.10.9, 2023.10.15, 2024.10.8, 2025.10.2
  • aimeos grapesjs_cms 2021.10.8, 2022.10.9, 2023.10.15, 2024.10.8, 2025.10.2

Is CVE-2025-66468 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
11mo ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
NVD 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
GitHub 3.1 7.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist aimeos/ai-cms-grapesjs
>=2021.04.1, <2021.10.8
>=2022.04.1, <2022.10.9
>=2023.04.1, <2023.10.15
>=2024.04.1, <2024.10.8
>=2025.04.1, <2025.10.2
2021.10.8
2022.10.9
2023.10.15
2024.10.8
2025.10.2

Affected products

  • aimeos ai-cms-grapesjs

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.