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

> Authenticated attackers can delete arbitrary files via directory traversal in the Seeds acmailer plugin.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:N/I:P/A:P`)
- **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:** 19 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-43qg-hpjm-xmxr

## What is CVE-2015-2971?

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

### Official description

Directory traversal vulnerability in Seeds acmailer before 3.8.18 and 3.9.x before 3.9.12 Beta allows remote authenticated users to delete arbitrary files via a crafted string.

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

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

It affects 1 product.


Products: Seeds Acmailer.

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

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

## Is CVE-2015-2971 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-1142](https://insights.sbomify.com/CVE-2016-1142/): Command injection in n/a (critical 9.1)
- [CVE-2014-3896](https://insights.sbomify.com/CVE-2014-3896/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2971 is a medium-severity path traversal vulnerability in n/a, published on 19 Jul 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-2971 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-2971/ (Markdown: https://insights.sbomify.com/CVE-2015-2971/index.md)
```

## Sources

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

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