# CVE-2026-124434: Grav Lightbox Gallery 1.1.0 before 1.3.2 File Read via Shortcode Media Actions


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-5h77-jjr5-889r, GHSA-jq4h-4q3q-hr32

## What is CVE-2026-124434?

CVE-2026-124434 is a high-severity vulnerability in getgrav grav, published on 8 Nov 2026. 

### Official description

Grav Lightbox Gallery plugin 1.1.0 before 1.3.2 on Grav 2.x calls any medium method named in image, thumb or thumb_options shortcode values without core's allowed media action check. A page editor can chain addMetaFile with value, toYaml or toJson to read server-readable YAML files, such as account password hashes, 2FA secrets and API keys, into a publicly viewable page.

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

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


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

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

## Is CVE-2026-124434 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124434 is a high-severity vulnerability in getgrav grav, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124434 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-124434/ (Markdown: https://insights.sbomify.com/CVE-2026-124434/index.md)
```

## Sources

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

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