# CVE-2026-53757: Emlog: Zip Slip Path Traversal in Plugin/Template ZIP Upload Enables RCE

> Attackers can exploit a path traversal flaw in Emlog's ZIP extraction to overwrite configuration files and achieve remote code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-gjj4-37r4-mf5g

## What is CVE-2026-53757?

CVE-2026-53757 is a medium-severity path traversal vulnerability in emlog, published on 4 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Emlog is an open source website building system. In versions 2.6.29 and prior, the emUnZip() function extracts all ZIP entries via ZipArchive::extractTo() without validating entry paths for ../ traversal sequences. Only the first entry's subdirectory structure is checked. An attacker can overwrite arbitrary files on the server filesystem, including config.php for immediate RCE. At time of publication, there are no publicly known patches.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-53757 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53757 is a medium-severity path traversal vulnerability in emlog, published on 4 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53757 in the wild and no public exploit code.

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

## Sources

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

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