Skip to main content

Grav CMS CVE-2026-42842

MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-05-05 https://github.com/getgrav/grav GHSA-c2q3-p4jr-c55f
5.4
CVSS 3.1 · Vendor: https://github.com/getgrav/grav
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Attacker gains editor account
  2. Delivery
    Accesses page editor
  3. Exploit
    Injects payload in taxonomy field
  4. Install
    Stores malicious taxonomy value
  5. C2
    Admin opens any page editor
  6. Execute
    Payload renders in unescaped select dropdown
  7. Impact
    JavaScript executes in admin context
  8. Step 8
    Steals admin nonce via DOM access
  9. Step 9
    Executes privileged AJAX request
  10. Step 10
    Creates new admin account or modifies configuration

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Editor-level account with permission to create or edit pages and set taxonomy field values is required. The vulnerability is triggered when an administrator views or edits any page in the admin panel after the malicious taxonomy value has been stored; the XSS executes automatically without additional user interaction beyond the admin opening the page editor. Taxonomy fields must be enabled in the page type (default configuration). HttpOnly session cookie flag prevents direct session theft but does not prevent nonce theft or JavaScript-based admin action execution. The exploit requires that the Grav Form plugin is installed (default), that the select field template is used for taxonomy fields (default), and that the vulnerable code path rendering option display text with |raw is not overridden locally.

Impact

CVSS 5.4 (AV:N/AC:L/PR:L/UI:R/S:C) indicates network-accessible, low-complexity exploitation requiring editor-level privileges and user interaction (admin viewing the page editor). However, the actual risk profile is elevated beyond this score. The attack is highly practical: editors are a common role in CMS deployments, user interaction is guaranteed (admins regularly edit pages), and the impact is severe-the XSS can steal admin nonce tokens and execute arbitrary admin actions despite HttpOnly session cookies. The cross-page nature of the vulnerability means a single malicious payload compromises the entire admin panel for all administrators. EPSS and KEV status are not provided in the input, but the detailed maintainer note confirming fixes across two repositories (grav-plugin-form and Grav core) with specific commit hashes demonstrates vendor awareness and active remediation. The existence of a proof-of-concept in the CVE description confirms demonstration feasibility. This is a real priority for environments running Grav versions prior to the patch, particularly those with untrusted editors or where privilege escalation to admin is a significant operational risk.

Exploit ScenarioDerived

An attacker with editor credentials navigates to the page creation interface, sets a page title, and injects a malicious payload into a taxonomy tag field: </option></select><img src=x onerror=alert('XSS')>. This payload closes the select dropdown context and injects an unquoted event handler that bypasses Grav's XSS detection regex. When any administrator later opens any page editor (not just the malicious page), the shared global taxonomy pool renders this payload unescaped in the select dropdown, and the injected JavaScript executes in the admin's browser with their session privileges. The attacker can then use JavaScript to steal the admin nonce token and perform unauthorized actions such as creating new admin users or modifying site configuration.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 05, 2026

Stored cross-site scripting in Grav CMS Form plugin allows editor-level users to inject arbitrary JavaScript via taxonomy tag and category values that execute in administrator browsers when viewing any page in the admin panel. The vulnerability exploits unescaped Twig |raw filters in the select field template combined with a bypassable XSS detection regex, enabling privilege escalation through nonce theft and unauthorized admin actions. Vendor-released patch available in grav-plugin-form 9.0.1 and Grav core 2.0.0-beta.2.

RemediationAI

Upgrade Grav CMS to version 2.0.0-beta.2 or later, which includes the patched grav-plugin-form 9.0.1 automatically via dependency resolution. The primary fix removes all |raw Twig filters from the select field template (select.html.twig), ensuring taxonomy values are escaped by default. For Grav 2.0 users, also verify that the patched form plugin version 9.0.1 is installed, as the select.html.twig file in that plugin contains the critical fix. Core fixes include tightening the on_events regex in Security::detectXss() to reject unquoted event handlers, and adding svg, math, option, and select to the default security.xss_dangerous_tags list to prevent context-breaking exploits. Sites unable to upgrade immediately should restrict editor-level taxonomy field permissions if possible, or apply output encoding at the application level by modifying select.html.twig locally to remove the |raw filters-however, this is not a supported configuration and may break during future updates.

Affected Packages

composer getgrav/grav fix: 2.0.0-beta.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in composer

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Form plugin's select field template (select.html.twig) renders option values using Twig's |raw filter, which bypasses HTML escaping. Taxonomy fields are implemented as select dropdowns where option display text is rendered unescaped, although attribute values are properly encoded by browser defaults. The vulnerability is amplified by Grav's global taxonomy pool: a malicious taxonomy value added to any page propagates to every page editor's taxonomy dropdown, making this cross-page stored XSS. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation). Additionally, Grav's built-in Security::detectXss() function contained a regex bypass in the on_events pattern that required quotes or whitespace around event handler attributes, allowing payloads like onerror=alert(1)> (without quotes or trailing space) to evade detection. The exploit also closes the <option>/<select> context using tags not flagged as dangerous, further bypassing the detection layer.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (https://github.com/getgrav/grav) PRIMARY 5.4 MEDIUM
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Primary rating from Vendor (https://github.com/getgrav/grav) · only source for this CVE.

CVSS VectorVendor: https://github.com/getgrav/grav

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

Summary

A Stored Cross-Site Scripting (XSS) vulnerability exists in the Grav CMS Form plugin's select field template. Taxonomy tag and category values are rendered with the Twig |raw filter in the admin panel, bypassing the global autoescape protection. An editor-level user can inject arbitrary JavaScript that executes in any administrator's browser session when they view or edit any page in the admin panel.

Additionally, Grav's built-in XSS detection (Security::detectXss()) can be bypassed by using payloads that close the <option>/<select> context and use unquoted event handlers - the on_events regex fails to match event handlers without quotes or trailing spaces before >.

Important

  • The vulnerability is in the Form plugin (select.html.twig), which is installed by default with Grav
  • The XSS is cross-page: a malicious taxonomy value on one page executes when an admin edits any page, because taxonomy options are rendered from a shared global pool
  • An editor can exploit this without any other vulnerability - taxonomy fields are not in the server-side restricted fields list
  • The HttpOnly flag on session cookies prevents direct session theft, but the XSS can steal the admin nonce and perform privileged actions via JavaScript

Permissions Needed

  • Editor: can create or edit pages and set taxonomy tag/category values

Details

The Form plugin's select field template renders option values using the |raw Twig filter, which outputs content without HTML escaping:

File: user/plugins/form/templates/forms/fields/select/select.html.twig

twig
{
# Line 55 #}
 avalue|raw

{
# Line 65 #}
 suboption|t|raw

{
# Line 72 #}
 item_value|t|raw

The taxonomy field in the page editor uses this select template. When a page has taxonomy values (tags, categories), these values are populated as <option> elements in the select dropdown. The value attribute is properly escaped by the browser's attribute encoding, but the display text between <option> tags is rendered raw:

html
<option value="&lt;script&gt;alert(1)&lt;/script&gt;"><script>alert(1)</script></option>

Since taxonomy options are collected globally across all pages (to provide autocomplete/selection), a malicious taxonomy value on any page will appear in the taxonomy dropdown of every page editor - making this a cross-page stored XSS.

The server-side field restriction in the flex-objects plugin only blocks ['form', 'forms', 'process', 'twig'] for non-super users. Taxonomy fields are not restricted, so editors can freely set arbitrary taxonomy values.

XSS Detection Bypass

Grav's Security::detectXss() checks for dangerous_tags (e.g., <script>, <iframe>), on_events (event handlers), and invalid_protocols (e.g., javascript:). However, the on_events regex:

php
'on_events' => '#(<[^>]+[a-z\x00-\x20"\'\/)(?:on[a-z]+)\s*=[\s|\'"'].*[\s|\'"']>#iUu'

requires either quotes around the handler value or a trailing space before >. An unquoted handler like onerror=alert(1)> (no space before >) bypasses this check entirely.

Combined with </option></select> to break out of the select context (neither tag is in dangerous_tags), the full payload evades all three detection layers and triggers no XSS warning in the admin panel.

PoC

Step 1: Login as Editor

Navigate to http://TARGET/admin/ and authenticate with editor credentials.

Step 2: Create a Page with Malicious Taxonomy
  • Go to Pages → Add → Add Page
  • Title: XSS via editor
  • Go to Options Tap
  • On Taxonomies, Add tag:
</option></select><img src=x onerror=alert('XSS-via-editor')>

This payload:

  • Closes </option></select> to break out of the select dropdown context
  • Injects an <img> tag with an unquoted onerror handler (bypasses on_events regex)
  • Is not in the dangerous_tags list (no <script>, <iframe>, etc.)
  • Triggers no XSS warning in the admin panel

<img width="1221" height="857" alt="image" src="https://github.com/user-attachments/assets/6223cbb2-f04b-46bd-89ce-828c89ad77ab" />

Step 3: Trigger the XSS

When any administrator navigates to the page editor of any page (not just the malicious one), the JavaScript executes immediately.

<img width="1224" height="856" alt="image" src="https://github.com/user-attachments/assets/f008b0f2-dedb-4b22-a74a-cdc0d7325cb4" />

The XSS fires because taxonomy tag options are collected globally across all pages and rendered with |raw in the select dropdown template. The payload breaks out of the <option> context, and the browser renders the <img> tag as a regular DOM element.

Impact

  • Session hijacking: While HttpOnly prevents direct cookie theft, the XSS can steal the admin nonce token and perform any admin action via AJAX requests
  • Privilege escalation: An editor can perform admin-only actions (create users, modify system configuration, install plugins) through the hijacked admin session
  • Cross-page impact: A single malicious taxonomy value affects the entire admin panel - every page editor view is compromised

---

Maintainer note - fix applied (2026-04-24)

Fixed across two repos:

  1. grav-plugin-form 9.0.1 (commit 6bffb4c) - the primary fix. All four |raw filters in templates/forms/fields/select/select.html.twig (placeholder, avalue, suboption, item_value) have been removed. Option labels - including taxonomy values that propagate cross-page through the admin's shared selection pool - now go through Twig's default escaper, so a lower-privileged editor can no longer inject script that runs in an admin's browser when they open any page editor.
  2. Grav core on the 2.0 branch (commit 5a12f9be8, ships in 2.0.0-beta.2) - closes the detection-bypass half of the report. The on_events regex in Security::detectXss() is tightened so unquoted handlers like onerror=alert(1)> are flagged (see separate GHSA-9695-8fr9-hw5q), and option/select have been added to default security.xss_dangerous_tags so </option></select>… tripwires the detector (see separate GHSA-w8cg-7jcj-4vv2).

Sites running admin2 on Grav 2.0.0-beta.2 get the 9.0.1 form plugin automatically via its existing dependency graph.

Files:

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Threat Intel
1
1 source
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Affected Products (CPE)CVE.org

pkg:composer/getgrav_grav

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy