# CVE-2026-46687: Emlog Local File Inclusion (LFI)

> An authenticated author can exploit a path traversal vulnerability in Emlog to include arbitrary local PHP files, potentially leading to code execution or data disclosure.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-9h6g-q584-9vfg

## What is CVE-2026-46687?

CVE-2026-46687 is a high-severity path traversal vulnerability in emlog, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Emlog is an open source website building system. In 2.6.13 and earlier, the article publishing interface stores a path-traversal template parameter from api_controller.php without validation, and log_controller.php later checks file_exists and calls include View::getView($template), allowing an authenticated author to include an arbitrary local .php file when an article is viewed. No fixed version is currently identified.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), CWE-24 (Path Traversal: '../filedir')

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


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

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

## Is CVE-2026-46687 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46687 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46687 is a high-severity path traversal vulnerability in emlog, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46687 exists.

Affected product: emlog. 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-46687/ (Markdown: https://insights.sbomify.com/CVE-2026-46687/index.md)
```

## Sources

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

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