Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain low-privilege Grav account
-
DeliveryAccess Flex Objects plugin settings endpoint
-
ExploitCraft ZIP archive containing PHP webshell
-
InstallSubmit upload with array notation routine name
-
C2Bypass string-based validation check
-
ExecuteunZip routine writes PHP file to web root
-
ImpactRequest planted file via HTTP to execute code
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid authenticated user session with at least low-privilege access to the Grav admin interface, consistent with CVSS PR:L. The Flex Objects plugin must be installed and enabled on the target instance - sites that do not use this plugin are not affected. The bypass relies on supplying the unZip routine name in PHP array notation rather than string notation in the settings validation request; no race condition, special network position, or out-of-band channel is required. Exploitation is limited by: (1) the authentication gate - unauthenticated remote attackers cannot trigger this without valid credentials; (2) the Flex Objects plugin dependency - the vulnerable code path is absent if the plugin is not active; (3) web server filesystem permissions - if the PHP process does not have write access to the web root (a non-default hardened configuration), the file-write step will fail and code execution will not occur. |
| Impact | The CVSS 4.0 score of 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) accurately represents the combination of network accessibility and full-system impact; the primary risk mitigator embedded in the vector is PR:L, meaning exploitation is gated behind a valid authenticated session. The vulnerability is not listed in the CISA KEV catalog and no public exploit code has been identified at time of analysis, suggesting it has not yet seen mass opportunistic exploitation. However, the technical disclosure of the exact bypass mechanism - array notation substitution - is specific enough that a skilled attacker can reproduce it without a published POC, elevating practical risk above what the absence of KEV listing alone implies. EPSS score data was not supplied in the available intelligence, so probability-of-exploitation modeling cannot be quantified here. The most significant real-world risk concentrator is Grav deployments that permit open self-registration or that expose the admin panel to untrusted users; in tightly controlled single-author or closed-team deployments the effective risk is substantially lower. No CVSS vector conflict or data inconsistency was identified. |
| Exploit ScenarioDerived | An attacker with a low-privilege registered account - such as a site editor or contributor - logs into an exposed Grav admin panel running a vulnerable version with the Flex Objects plugin active. The attacker constructs a ZIP archive embedding a PHP webshell, then submits an upload request to the Flex Objects settings endpoint with the unZip routine name supplied in array notation to bypass string-based validation. The routine extracts the archive, writing the webshell into the web root; the attacker then sends a direct HTTP GET request to the planted file path and receives an interactive shell running as the web server process. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 14, 2026
Remote code execution in Grav CMS before 2.0.13 allows authenticated low-privilege users to plant and execute arbitrary PHP files on the server by exploiting a validation bypass in the Flex Objects plugin. The attacker crafts a ZIP archive containing PHP code, circumvents routine-name validation by substituting array notation for the expected string notation, and triggers the unZip routine to write the payload directly into the web root where it becomes immediately executable via HTTP. No public exploit has been identified at time of analysis, but the precise bypass technique disclosed in the advisory substantially lowers the barrier to exploitation for any attacker holding valid credentials.
RemediationAI
Upgrade Grav CMS to version 2.0.13 or later; this is the vendor-confirmed fix as documented in the GitHub Security Advisory GHSA-r94f-hx44-8jqf at https://github.com/getgrav/grav/security/advisories/GHSA-r94f-hx44-8jqf. If immediate upgrade is not operationally feasible, disable the Flex Objects plugin entirely to eliminate the vulnerable code path - note that any site features built on Flex Objects will stop functioning until the plugin is re-enabled post-upgrade. As a defense-in-depth measure regardless of upgrade status, audit and restrict the set of user accounts that hold write-level access to Flex Objects settings, and disable open user self-registration if it is not a business requirement, since exploitation requires PR:L authenticated access. Additionally, configure the web server process to run under a user with minimal filesystem permissions and, where possible, make the web root non-writable by the PHP process at the OS level; this would block the file-write step even if the plugin bypass is triggered, though it is an atypical hardening posture that may break legitimate upload features.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in composer, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Grav CMS is a flat-file PHP content management system; rather than a database, it stores content as files, and all user-accessible pages are served as PHP from the web root. The vulnerable component is the Flex Objects plugin, which provides dynamic object management and exposes settings-validation endpoints to authenticated users. The root cause is CWE-94 (Code Injection): the settings handler validates the name of the routine to invoke using string-based comparison, but that check is bypassed when the caller supplies the routine name in PHP array notation rather than string notation. Once bypass succeeds, the handler invokes the unZip routine against an attacker-controlled archive, extracting files - including arbitrary .php files - into the web root without further sanitization. Because the PHP process that serves Grav also owns the web root, every extracted file is immediately reachable and executable over HTTP. The affected CPE is cpe:2.3:a:getgrav:grav:*:*:*:*:*:*:*:*, covering all releases prior to 2.0.13.
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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Network-accessible upload endpoint; PR:L because a valid authenticated session is required; S:U consistent with CVSS 4.0 SC:N/SI:N/SA:N indicating no lateral scope change.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Grav CMS before 2.0.13 contains a remote code execution vulnerability in the Flex Objects plugin settings validation that allows authenticated users to execute arbitrary code by uploading a ZIP file containing PHP code. Attackers can bypass routine name validation by using array notation instead of string notation, call the unZip routine with a malicious archive, and write PHP files to the web root for execution.
Latest POC
1 public PoC link from github
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
Grav CMS versions before 2.0.13 contain a remote code execution vulnerability in the Flex Objects plugin that allows authenticated low-privilege users to upload and execute arbitrary PHP code on web servers. This exposes any organization running vulnerable versions with user account creation enabled to server compromise and potential lateral movement into backend systems.
No vendor-released patch identified at time of analysis. Disable the Flex Objects plugin if unused; prevent PHP execution in upload/cache directories via web server configuration; implement whitelist-based file-type validation at the application layer; monitor for unexpected PHP files written to web-accessible paths; restrict creation of new user accounts with upload privileges; deploy WAF rules to inspect ZIP file contents for embedded PHP code.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Server-side template injection (SSTI) in Grav (getgrav/grav) prior to 1.8.0-beta.27 allows an authenticated attacker hol
Broken access control in Grav CMS (CWE-285) before 1.8.0-beta.27 lets an authenticated editor-level user escalate their
A Remote Code Execution (RCE) vulnerability in Grav CMS v1.7.48 allows an authenticated admin to upload a malicious plug
Grav is a file-based Web platform. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low a
GravCMS 1.10.7 allows unauthenticated remote attackers to write arbitrary YAML configuration files, leading to full serv
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
Remote code execution in Grav CMS before 2.0.15 allows attackers holding page-edit or blueprint-config privileges to wri
Vertical privilege escalation in Grav CMS before 2.0.14 lets a delegated administrator holding only the admin.users perm
Stored cross-site scripting in Grav CMS before 2.0.15 lets authenticated editors smuggle JavaScript event handlers past
Server-side request forgery (SSRF) in Grav CMS versions prior to 1.7.49.5 allows remote authenticated attackers to make
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
Grav is an open-source, flat-file content management system. Rated high severity (CVSS 8.8), this vulnerability is remot
EUVD-2026-58633
GHSA-r94f-hx44-8jqf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB