Advisory record · GHSA-vfmf-q6x9-cw96

Grav: detectXss() misses an event-handler attribute after an unpaired quote in an unquoted attribute value, giving stored XSS

CVSS 9.3 CriticalCriticalEPSS 0.0039 · 33rd percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 17 Sept 2026, 20:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
getgrav/gravPackagist<2.0.152.0.15
Identifiers
GHSA-vfmf-q6x9-cw96 · CVE-2026-75828 · PKSA-tr1n-vmpf-rmt6
Weakness (CWE)
CWE-79
Published
17 Sept 2026
Updated
17 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Grav versions before 2.0.15 are affected by a stored cross-site scripting flaw in the detectXss() check, where an event-handler attribute placed after an unpaired quote inside an unquoted attribute value is not detected. An authenticated content editor without super-admin rights could store such markup in page content, which would then run script for visitors who view the page. The source says the issue was found and confirmed by replicating the detector, and it suggests upgrading to Grav 2.0.15, which is listed as the fixed version.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0039, the 33rd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:55 UTC First seen by agentprime
  2. 31 Oct 2026, 13:55 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.