# CVE-2013-6827: Path traversal in n/a

> Remote attackers with low privileges can read arbitrary files on the server via path traversal in the message viewing component.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/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:** 20 Nov 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fhcv-fhj5-x6px

## What is CVE-2013-6827?

CVE-2013-6827 is a medium-severity path traversal vulnerability in n/a, published on 20 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Absolute path traversal vulnerability in admin/viewmsg.php in PineApp Mail-SeCure allows remote attackers to read arbitrary files via a full pathname in the msg parameter.

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

## Which versions are affected by CVE-2013-6827?

It affects 1 product.


Products: Pineapp Mail-Secure.

## How do I fix CVE-2013-6827?

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

## Is CVE-2013-6827 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4987](https://insights.sbomify.com/CVE-2013-4987/): Command injection in n/a (high 8.5)
- [CVE-2013-6829](https://insights.sbomify.com/CVE-2013-6829/): Command injection in n/a (high 7.5)
- [CVE-2013-6828](https://insights.sbomify.com/CVE-2013-6828/): Auth bypass in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6827 and fix it if it is affected.

What it is: CVE-2013-6827 is a medium-severity path traversal vulnerability in n/a, published on 20 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6827 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-2013-6827/ (Markdown: https://insights.sbomify.com/CVE-2013-6827/index.md)
```

## Sources

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

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