# CVE-2026-117566: EasyImages2.0 through 2.8.6 Unauthenticated Path Traversal via down.php, thumb.php and info.php


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-59pp-4mv4-4j8f

## What is CVE-2026-117566?

CVE-2026-117566 is a medium-severity vulnerability in icret EasyImages2.0, published on 27 Oct 2026. 

### Official description

EasyImages2.0 through 2.8.6 contains an unauthenticated path traversal vulnerability in app/down.php, app/thumb.php and app/info.php that allows reading files outside the upload directory. Attackers can supply ../ sequences in the dw, history or img parameters to read files with allowed upload extensions from the server.

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

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


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

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

## Is CVE-2026-117566 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117566 is a medium-severity vulnerability in icret EasyImages2.0, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117566 in the wild and no public exploit code.

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

## Sources

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

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