# CVE-2015-2071: Path traversal in n/a

> Authenticated attackers can read arbitrary files via path traversal in the blog export feature of SamePage Enterprise Edition.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A: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:** 24 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m43g-2rqm-rjc3

## What is CVE-2015-2071?

CVE-2015-2071 is a medium-severity path traversal vulnerability in n/a, published on 24 Feb 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in cm/newui/blog/export.jsp in eTouch SamePage Enterprise Edition 4.4.0.0.239 allows remote authenticated users to read arbitrary files via a .. (dot dot) in the filepath parameter.

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

## Which versions are affected by CVE-2015-2071?

It affects 1 product.


Products: Etouch Samepage.

## How do I fix CVE-2015-2071?

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

## Is CVE-2015-2071 being exploited?

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

Public exploit code:

- eTouch SamePage 4.4.0.0.239 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-2070](https://insights.sbomify.com/CVE-2015-2070/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2071 and fix it if it is affected.

What it is: CVE-2015-2071 is a medium-severity path traversal vulnerability in n/a, published on 24 Feb 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-2071 in the wild and no public exploit code.

Affected product: n/a. 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-2015-2071/ (Markdown: https://insights.sbomify.com/CVE-2015-2071/index.md)
```

## Sources

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

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