CVE-2026-112780 getgrav CVE debrief

Who should care

Page editors, system administrators, and security teams responsible for Grav installations should assess exposure and verify page editor permissions and Flex form field renaming restrictions.

Why it matters

CVE-2026-112780 is a critical vulnerability in Grav 2.0.15 before 2.2.2 that allows page editors to call arbitrary public static methods, potentially leading to directory deletion, file overwriting, and file reading. Page editors, system administrators, and security teams should assess exposure and verify page editor permissions and Flex form field renaming restrictions to prevent exploitation.

• Arbitrary static method calls can lead to directory deletion, file overwriting, and file reading.
• Page editors with page-edit permission are at risk of being exploited.
• System administrators need to verify and restrict Flex form field renaming to prevent arbitrary static method calls.
• Security teams should monitor page editor activity for suspicious Flex form field renaming.

Technical summary

The Grav 2.0.15 before 2.2.2 contains an allowlist bypass vulnerability that allows page editors to call arbitrary public static methods by renaming Flex form fields with replace-name@. Attackers with page-edit permission can smuggle data-*@ directives past the callable check to invoke Folder::delete, Folder::move, or Utils::download, deleting directories, overwriting files, or reading files. The vulnerability is caused by a flawed allowlist mechanism that fails to properly validate Flex form field renaming, allowing attackers to bypass the callable check and invoke arbitrary public static methods.

Defensive priority

Page editors with page-edit permission should verify and restrict Flex form field renaming to prevent arbitrary static method calls.

Recommended defensive actions

• Verify and restrict Flex form field renaming to prevent arbitrary static method calls
• Update Grav to version 2.2.2 or later
• Monitor page editor activity for suspicious Flex form field renaming
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the allowlist bypass vulnerability in Grav 2.0.15 before 2.2.2, which allows page editors to call arbitrary public static methods by renaming Flex form fields with replace-name@.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.