# CVE-2026-112781: Grav 2.0.0 before 2.2.2 Information Disclosure via Form config-*@ Directives

> Page editors can expose sensitive configuration data like passwords and salts to all visitors by manipulating form directives.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-8wwq-x3w5-fxmw, GHSA-gffw-347v-3rhv

## What is CVE-2026-112781?

CVE-2026-112781 is a high-severity vulnerability in getgrav grav, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grav from 2.0.0 before 2.2.2 contains an information disclosure vulnerability that allows page editors to read protected configuration by adding config-*@ directives to page frontmatter forms. Attackers with page-edit permission can bypass the Twig sandbox config_denied_paths redaction to expose security.salt, plugin credentials, and Redis passwords to all visitors.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-112781?


## How do I fix CVE-2026-112781?

No fix has been published for CVE-2026-112781 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112781 being exploited?

There is no known exploitation of CVE-2026-112781 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112781 and fix it if it is affected.

What it is: CVE-2026-112781 is a high-severity vulnerability in getgrav grav, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112781 in the wild and no public exploit code.

Affected product: getgrav grav. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112781/ (Markdown: https://insights.sbomify.com/CVE-2026-112781/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112781
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112781
- OSV: https://osv.dev/vulnerability/CVE-2026-112781

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112781/
Summaries are generated and may contain mistakes; the official description above is the record.