Medium

Grav: Stored XSS via quoted-attribute bypass in detectXss

  • Disclosed: 17.09.2026
  • Updated: 11.10.2026 10:22

Summary

A page editor without admin.super can place an event handler after a > inside a quoted attribute. Grav accepts and stores the page, then executes the handler in the application origin when a visitor opens it.

Details

Security::detectXss() (system/src/Grav/Common/Security.php:253) anchors the on_events scan at < and uses [^>]*?, which cannot cross the first literal >. When that character is inside a quoted value, the browser keeps the tag open and parses the later onerror attribute, so the detector and browser disagree. AdminController::savePage() relies on this detector when saving content from page editors outside the admin.super whitelist.

PoC

I reproduced this with getgrav/grav 2.0.11 (ad9709f865b09b68798fb1ac375b484a8cc1d892), Admin 1.10.52, and Quark 2 1.1.4.

  1. Sign in as a user with admin.login and admin.pages, but without admin.super.
  2. Create or edit /xsstest and save this page body:
html
<img src=x title=">" onerror=alert(document.domain)>
  1. Open /xsstest in a private browser window.

The save succeeds and the visitor sees an alert containing the site domain. With the body changed to <img src=x onerror=alert(1)>, the same endpoint rejects it with XSS issue detected and does not store it.

Impact

A page editor can execute JavaScript in the origin of every user who views the stored page, including unauthenticated visitors.

Anticipated objection and response

Although the detectXss() docblock describes it as a heuristic that cannot catch every XSS, this check is the storage-time boundary for page editors outside the default security.xss_whitelist of admin.super. The same endpoint rejects a plain handler but accepts this executable form, allowing a lower-trust editor to cross the boundary the check is intended to enforce.

Suggested fix

Prefer an HTML tokenizer or sanitizer that rejects event-handler attributes on parsed elements. If the existing tripwire remains, make its tag scan quote-aware instead of treating every > as a boundary. Add double-quoted and single-quoted regression cases plus the rejected plain-handler control.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package getgrav/grav >= 1.5.2, < 2.0.13 2.0.13

References

CVSS score 5.4/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Weakness (CWE)
CWE-79
Platform
Composer
Package
getgrav/grav
Disclosed
17.09.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-269c-h76q-8cxw - CC BY 4.0

Vulnerability history: getgrav/grav

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (99) in the archive
Total entries
99
First → latest
11.2019 09.2026
Without a fix
6
Exploited in attacks
0

Severity breakdown

  • Critical 7
  • High 47
  • Medium 41
  • Low 4

Disclosures per year

  1. 2019: 1
  2. 2020: 1
  3. 2021: 4
  4. 2022: 10
  5. 2023: 5
  6. 2024: 8
  7. 2025: 23
  8. 2026: 47
Severity:
  1. High · 8.8 CVE-2026-72819 < 2.0.13 2.0.13
  2. Grav: Stored XSS via quoted-attribute bypass in detectXss this entry
    Medium · 5.4 CVE-2026-72832 >= 1.5.2, < 2.0.13 2.0.13
  3. High CVE-2026-53653 >= 2.0.0-beta.1, < 2.0.0-rc.8, < 1.7.53 2.0.0-rc.8, 1.7.53
  4. High · 8.9 CVE-2026-42611 < 2.0.0-beta.2 2.0.0-beta.2
  5. High · 8.5 CVE-2026-42612 < 2.0.0-beta.2 2.0.0-beta.2
  6. Critical · 9.4 CVE-2026-42613 < 2.0.0-beta.2 2.0.0-beta.2
  7. Critical · 9.1 CVE-2025-66844 <= 1.7.49.5 no fix
  8. High CVE-2025-66298 < 1.8.0-beta.27 1.8.0-beta.27
  9. High CVE-2025-66294 < 1.8.0-beta.27 1.8.0-beta.27
  10. High · 8.5 CVE-2025-66300 < 1.8.0-beta.27 1.8.0-beta.27
  11. High · 8.8 CVE-2025-66299 < 1.8.0-beta.27 1.8.0-beta.27
  12. High · 8.5 CVE-2024-34082 < 1.7.46 1.7.46
  13. High · 8.8 CVE-2024-28119 < 1.7.45 1.7.45
  14. High · 8.8 CVE-2024-28118 < 1.7.45 1.7.45
  15. High · 8.8 CVE-2024-28117 < 1.7.45 1.7.45
  16. High · 8.8 CVE-2024-27921 < 1.7.45 1.7.45
  17. High · 8.8 CVE-2024-27923 < 1.7.43 1.7.43
  18. High · 7.2 CVE-2023-37897 < 1.7.42.2 1.7.42.2
  19. High · 7.2 CVE-2023-34448 < 1.7.42 1.7.42
  20. High · 7.2 CVE-2023-34252 < 1.7.42 1.7.42
  21. Critical · 9.1 CVE-2023-34251 < 1.7.42 1.7.42
  22. High · 7.2 CVE-2022-2073 < 1.7.34 1.7.34
  23. High · 8.1 CVE-2020-29555 >= 1.7.0-beta.1, <= 1.7.0-rc.17, < 1.6.30 1.6.30
  24. High · 8.8 CVE-2020-29553 >= 1.7.0-beta.1, <= 1.7.0-rc.17, < 1.6.30 1.6.30
  25. High · 7.1 CVE-2022-0970 < 1.7.31 1.7.31
  26. High · 8.8 CVE-2021-3924 <= 1.7.24 no fix
  27. High · 8.4 CVE-2021-29440 < 1.7.11 1.7.11

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.