# CVE-2025-15066: Arbitrary File Download through Path Traversal in Innorix WP

> Attackers can download arbitrary files if the exam directory exists, exposing sensitive data in Innorix WP.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-69jh-5qjp-fcx9

## What is CVE-2025-15066?

CVE-2025-15066 is a medium-severity path traversal vulnerability in Innorix WP, published on 29 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), Missing Authorization vulnerability in Innorix WP allows Path Traversal.This issue affects Innorix WP from All versions If the "exam" directory exists under the directory where the product is installed (ex: innorix/exam)

Weakness: CWE-862 (Missing Authorization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-15066?


## How do I fix CVE-2025-15066?

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

## Is CVE-2025-15066 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15066 and fix it if it is affected.

What it is: CVE-2025-15066 is a medium-severity path traversal vulnerability in Innorix WP, published on 29 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15066 in the wild and no public exploit code.

Affected product: Innorix WP. 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-2025-15066/ (Markdown: https://insights.sbomify.com/CVE-2025-15066/index.md)
```

## Sources

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

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