CVE-2026-75834: getgrav grav · Cross-site Scripting
Affects getgrav gravSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.0.14 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.14
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade grav and getgrav/grav to 2.0.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| getgravgrav | Affected
| Fixed in
|
GitHubgetgrav/gravpkg:github/getgrav/gravOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Grav version 2.0.14. Users should upgrade to version 2.0.14 or later to remediate this vulnerability. No other mitigations are specified. Patch status is confirmed by the versioning information indicating the vulnerability is fixed in 2.0.14.
Description
Grav versions before 2.0.14 contain a stored cross-site scripting (XSS) vulnerability in the Security::detectXss() function. This flaw allows an authenticated user with page-edit permissions to inject malicious JavaScript that executes in the browsers of visitors viewing the affected page. The vulnerability arises because invalid UTF-8 bytes cause the XSS detection patterns to fail silently, bypassing the save-time XSS safety checks.