CVE-2026-75827: Grav before 2.0.15 Arbitrary File Write via error_log
Grav before 2.0.15 contains an arbitrary file write vulnerability in the Blueprint dynamic-data bare-function validation that uses an incomplete denylist instead of a positive allowlist. Attackers with page-edit or blueprint-config access can invoke the error_log function through a data directive to append PHP payloads to web-accessible files, achieving remote code execution.
Security readout for executives and security teams
Plain-English summary
A flaw in Grav versions before 2.0.15 can let an attacker with page-edit or blueprint-configuration access write malicious PHP into a web-accessible file. Successful abuse could give the attacker control of the website and its data. Internet reachability alone may not be sufficient because the description also identifies required content-management access.
Executive priority
Treat this as an urgent remediation item for affected Grav sites, especially public-facing or business-critical systems. Establish version and access exposure immediately, upgrade promptly, and investigate unexpected file changes. There is no supplied evidence of active exploitation, but the potential outcome is full website compromise.
Technical view
Blueprint dynamic-data bare-function validation uses an incomplete denylist. The error_log function can consequently be invoked through a data directive to append PHP content to web-accessible files, leading to code execution. The supplied CVSS 4.0 score is 9.3, although its PR:N metric conflicts with the description's stated access prerequisite.
Likely exposure
Exposure is limited to Grav installations running versions before 2.0.15. Risk is greatest where untrusted or compromised users have page-edit or blueprint-configuration access and the application can write to PHP-executable, web-accessible files. The supplied version data is imprecise, so confirm applicability against the vendor advisory.
Exploitation context
The bundle does not identify CVE-2026-75827 as a CISA KEV entry and provides no cited evidence of active exploitation. Exploitation is described as remotely achievable code execution after abusing authorized content or configuration capabilities; the exact privilege requirement should be reconciled with the PR:N CVSS metric.
Researcher notes
CWE-94 and the described arbitrary file-write path support a code-execution impact. Important uncertainty remains: the narrative requires page-edit or blueprint-config access, while the CVSS vector states PR:N. The affected-version structure also lists ambiguous endpoints. Use the vendor advisory as the authoritative source for precise version boundaries and prerequisites.
Mitigation direction
Upgrade affected Grav installations to version 2.0.15 or later, following the vendor advisory.
Restrict page-edit and blueprint-configuration access to trusted administrators until upgrades are complete.
Review vendor guidance for any additional containment or integrity-check recommendations.
Prioritize systems permitting application writes to web-accessible, PHP-executable locations.
Validation and detection
Inventory every Grav deployment and record its exact installed version.
Identify accounts and roles with page-edit or blueprint-configuration access.
Review web-accessible files for unexpected PHP additions or recent unexplained modifications.
Examine application, authentication, and web-server logs for suspicious content-management activity.
Confirm upgraded systems report Grav 2.0.15 or later.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code
Improper Control of Generation of Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.