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

> Remote attackers can execute arbitrary files via directory traversal in the Easy2Map WordPress plugin, requiring an upgrade to secure the site.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fvmx-w547-hmqf

## What is CVE-2015-7669?

CVE-2015-7669 is a critical path traversal vulnerability in n/a, published on 27 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in (1) includes/MapImportCSV2.php and (2) includes/MapImportCSV.php in the Easy2Map plugin before 1.3.0 for WordPress allow remote attackers to include and execute arbitrary files via the csvfile parameter related to "upload file functionality."

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

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

It affects 1 product.


Products: Easy2map Easy2map.

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

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

## Is CVE-2015-7669 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7668](https://insights.sbomify.com/CVE-2015-7668/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7669 is a critical path traversal vulnerability in n/a, published on 27 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7669 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-7669/ (Markdown: https://insights.sbomify.com/CVE-2015-7669/index.md)
```

## Sources

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

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