Skip to main content

Grav Data Manager CVE-2026-100673

| EUVDEUVD-2026-87767 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-09-26 VulnCheck GHSA-76r2-pr95-2295
8.4
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

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

  1. Access
    Submit crafted front-end form
  2. Delivery
    Store HTML payload in user/data entry
  3. Exploit
    Admin opens entry in classic admin panel
  4. Execution
    Script executes in admin session/origin
  5. Impact
    Hijack admin privileges and CSRF token

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

Requires the target Grav site to (1) run the Data Manager plugin version 1.0.1 through 1.4.4, (2) route front-end form submissions into the user/data store so an unauthenticated visitor can create a stored entry, and (3) use the classic Grav admin panel - sites using the Grav 2.0 Admin Next interface are NOT affected because it renders the same data through a correctly-escaping path. Payload triggering requires an administrator to open the malicious entry in the item-detail view: for list-type values (checkbox/multi-select) execution occurs on view with no further interaction, while for ordinary text fields it triggers on hover. The initial injection itself needs no authentication.

Impact

This is a genuine, moderately-high-risk stored XSS that crosses a privilege boundary. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N with subsequent-system SC:H/SI:L) scores 8.4 and is defensible: the initial injection is remote and unauthenticated (PR:N) because the payload is stored via an ordinary front-end form, and the passive user interaction (UI:P) reflects the administrator merely opening/viewing the entry - which for list/checkbox/multi-select fields fires with no action at all and for text fields fires on hover. The high subsequent-system confidentiality impact (SC:H) captures full compromise of the admin session in the classic admin panel, including the CSRF token, enabling attacker actions with administrator privileges. No exploitation-probability signals reinforce urgency: there is no EPSS score, no CISA KEV listing, and no public exploit identified at time of analysis - so this is a real priority driven by impact and low exploitation barrier, not by observed in-the-wild activity. Two limiting factors temper the raw score: the site must actually route front-end form submissions into user/data via Data Manager, and it must use the classic admin panel - the Grav 2.0 Admin Next interface is explicitly not affected because it escapes correctly.

Exploit ScenarioDerived

An attacker submits a public front-end form on a Grav site whose entries are stored to user/data, placing a crafted HTML/JavaScript payload (e.g. in a checkbox or multi-select value) into a saved data entry. When an administrator later opens that entry in the classic admin panel's item-detail view, the unescaped raw-filtered value executes as JavaScript in the admin's session and origin - automatically for list values, on hover for text fields. No public exploit code is currently identified, but the technique (Twig raw plus a strip_tags allowed-tag/attribute bypass) is straightforward to reproduce.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 26, 2026

Stored cross-site scripting in the Grav Data Manager plugin (getgrav/grav-plugin-datamanager) versions 1.0.1 through 1.4.4 allows an unauthenticated visitor to plant an HTML/JavaScript payload through a front-end form whose submissions are written into the user/data store; that payload is later rendered unescaped in the classic admin panel's item-detail view and executes in the administrator's browser session and origin, with access to that administrator's privileges and CSRF token. Exploitation requires a specific but realistic configuration chain: the site must route front-end form submissions into user/data, and the administrator must open the malicious entry in the classic Grav admin panel - sites running the Grav 2.0 Admin Next interface are not affected because it renders the same data through a separate, correctly escaping code path. The initial injection is unauthenticated (CVSS PR:N), while the privilege-boundary crossing needs administrator interaction (UI:R); payloads in list-type values such as checkboxes or multi-selects fire on view with no further interaction, whereas ordinary text fields fire on hover. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the issue is fixed in Data Manager 1.4.5.

RemediationAI

Vendor-released patch: upgrade the Grav Data Manager plugin to version 1.4.5 or later, which is the exact fixed release named by the vendor and in the GitHub security advisory (https://github.com/getgrav/grav/security/advisories/GHSA-863q-9v8v-m9fv); also see the VulnCheck advisory at https://www.vulncheck.com/advisories/grav-data-manager-before-1.4.5-stored-xss-via-item-detail-view. Where an immediate upgrade is not possible, the most effective compensating control is to stop using the classic Grav admin panel and switch administrators to the Grav 2.0 Admin Next interface, which renders the same stored data through a correctly escaping code path - the trade-off is a different administrative UX and the need to verify plugin compatibility. Secondary mitigations: block or remove any front-end form that writes submissions into the user/data store so unauthenticated visitors can no longer plant stored entries (this may break legitimate data-collection functionality and should be treated as a temporary measure), and until patched, treat any user/data content sourced from untrusted front-end input as hostile - inspect or purge suspicious entries before opening them in the classic item-detail view, and avoid hovering over untrusted text-field values or viewing untrusted list-type values. Restricting or putting the classic admin panel behind additional network controls reduces the reachable attack surface but does not fix the underlying escaping defect, so patching to 1.4.5 remains the primary remediation.

Affected VersionsENISA

grav 0 <1.4.5

Affected Packages

euvd grav fix: 1.4.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e. cross-site scripting) in the Grav Data Manager plugin's rendering layer. The item-detail view template (admin/templates/partials/item.html.twig) emits stored entry values with Twig's raw filter, disabling Twig's automatic contextual autoescaping, and in some paths applies a striptags('<br>') call first - a sanitization step that PHP's strip_tags() does not reliably neutralize, since it preserves allowed tags together with their attributes, allowing event-handler attributes to survive into the rendered markup. The plugin stores front-end form submissions in the user/data directory, so an unauthenticated submitter can persist attacker-controlled markup that is later reflected back in an administrative context. The security boundary crossed is the browser origin/session of the Grav admin: injected script runs with the administrator's session cookies, privileges, and CSRF token, enabling authenticated actions such as plugin/theme changes, configuration edits, or user creation. A mitigating architectural detail is that Grav 2.0's Admin Next interface renders the same stored data through a distinct, correctly escaping render path, so only the classic admin panel is vulnerable. Data provided identifies the affected platform CPE as cpe:2.3:a:getgrav:grav:*:*:*:*:*:*:*:* with the vulnerable plugin range mapped by ENISA EUVD to grav < 1.4.5; note that this plugin-version range (1.0.1-1.4.4) is the authoritative affected set, not the Grav core version.

Know when Grav 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 (VulnCheck) PRIMARY 8.4 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
vuln.today AI 8.2 HIGH

Unauthenticated remote injection (PR:N) via a stored payload that executes only when an admin views the entry (UI:R), crossing into the admin security context (S:C) to steal session/token (C:H, I:L).

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
Low
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Sep 26, 2026 - 14:02 EUVD
CVE Published
Sep 26, 2026 - 13:23 cve.org
HIGH 8.4

DescriptionCVE.org

The Grav Data Manager plugin (getgrav/grav-plugin-datamanager) versions 1.0.1 through 1.4.4 render stored data entries in the item-detail view (admin/templates/partials/item.html.twig) without escaping, applying Twig's raw filter - in some cases after a striptags('<br>') call that PHP's strip_tags() bypasses by preserving allowed tags together with their attributes. An unauthenticated visitor who submits a front-end form whose submissions are saved to user/data can store an HTML payload that executes as JavaScript in the session and origin of an administrator who later opens that entry in the classic admin panel, running with that administrator's privileges and CSRF token. Execution occurs without further interaction for list values (such as checkbox or multi-select fields) and on hover for ordinary text fields. Sites using the Grav 2.0 Admin Next interface are not affected, because it renders the same data through a separate, correctly escaping code path. The issue is fixed in Data Manager 1.4.5.

Technical POC Analysis

CWE-79 (stored cross-site scripting), in the Data Manager plugin's item-detail template admin/templates/partials/item.html.twig.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

Grav Data Manager plugin versions 1.0.1 through 1.4.4 contain a stored cross-site scripting issue that can allow an unauthenticated visitor to inject content later executed in an administrator's classic Grav admin panel session, with access to that administrator's privileges and CSRF token. No public exploit identified at time of analysis, but the required configuration chain is realistic and successful exploitation could compromise site integrity or administrator-controlled data. Leadership should prioritize remediation because the plugin may be present on Internet-facing Grav sites and affected administrators operate within a trusted session.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
Low
specific plugin for the niche Grav flat-file CMS, limited production footprint
Data Quality
6 sources
Confidence: High

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 HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
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.

Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.

More in Grav

View all
CVE-2025-66294 HIGH POC
8.7 Dec 01

Server-side template injection (SSTI) in Grav (getgrav/grav) prior to 1.8.0-beta.27 allows an authenticated attacker hol

CVE-2025-66301 HIGH POC
8.6 Dec 01

Broken access control in Grav CMS (CWE-285) before 1.8.0-beta.27 lets an authenticated editor-level user escalate their

CVE-2025-50286 HIGH POC
8.1 Aug 06

A Remote Code Execution (RCE) vulnerability in Grav CMS v1.7.48 allows an authenticated admin to upload a malicious plug

CVE-2024-34082 CRITICAL POC
9.9 May 15

Grav is a file-based Web platform. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low a

CVE-2021-47812 CRITICAL POC
9.8 Jan 16

GravCMS 1.10.7 allows unauthenticated remote attackers to write arbitrary YAML configuration files, leading to full serv

CVE-2026-65008 CRITICAL POC
9.3 Jul 21

Remote code execution in Grav CMS 2.0.4 (fixed in 2.0.7) lets an authenticated user holding the admin.pages or api.pages

CVE-2026-75827 CRITICAL POC
9.3 Aug 18

Remote code execution in Grav CMS before 2.0.15 allows attackers holding page-edit or blueprint-config privileges to wri

CVE-2026-75837 CRITICAL POC
9.3 Aug 18

Vertical privilege escalation in Grav CMS before 2.0.14 lets a delegated administrator holding only the admin.users perm

CVE-2026-75828 CRITICAL POC
9.3 Aug 18

Stored cross-site scripting in Grav CMS before 2.0.15 lets authenticated editors smuggle JavaScript event handlers past

CVE-2025-66844 CRITICAL POC
9.1 Dec 15

Server-side request forgery (SSRF) in Grav CMS versions prior to 1.7.49.5 allows remote authenticated attackers to make

CVE-2025-66299 HIGH POC
8.8 Dec 01

Grav is a file-based Web platform. Prior to 1.8.0-beta.27, Grav CMS is vulnerable to a Server-Side Template Injection (S

CVE-2026-72819 HIGH POC
8.7 Aug 14

Remote code execution in Grav CMS before 2.0.13 allows authenticated low-privilege users to plant and execute arbitrary

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