CVE-2026-75828
Stored XSS in Grav CMS detectXss allows authenticated editors to inject event handlers.
Is CVE-2026-75828 being exploited?
Not confirmed. CVE-2026-75828 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-75828?
CVE-2026-75828 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-75828?
Yes. A fix has been recorded for CVE-2026-75828. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-75828 affect?
CVE-2026-75828 affects Grav CMS < 2.0.15. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-75828?
Upgrade Grav to >=2.0.15; restrict editor roles; review recent content.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated editors can inject event handlers (e.g., onerror) causing stored XSS in visitors' browsers — session theft, CSRF, malware delivery.
Patch when possible
- affected< 2.0.15
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.