CVE-2026-75827 is an arbitrary file-write vulnerability in Grav versions before 2.0.15. Blueprint dynamic-data validation for bare PHP function callables uses an incomplete denylist rather than a strict allowlist. A user authorized to edit pages or configure Blueprints can invoke a non-denylisted function, including PHP's error logging functionality, through a dynamic-data directive. This permits attacker-controlled content to be appended to an attacker-chosen file location. Writing PHP content to a web-accessible or application-included file can lead to remote code execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity arbitrary file-append vulnerability in Grav's dynamic Blueprint data-provider handling. The insufficient denylist permits the PHP error_log function, allowing a low-privileged authenticated user able to edit page/frontmatter or blueprint configuration to write a PHP payload to a web-served or subsequently included file and obtain code execution.
An arbitrary file write vulnerability in Grav before 2.0.15 that can be leveraged to achieve remote code execution via the Blueprint dynamic-data bare-function validation and abuse of error_log.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.