# CVE-2011-5294: Path traversal in n/a

> Remote attackers can write arbitrary files via a crafted pathname in the SaveMessage method of the LEADSmtp ActiveX control.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jan 2015
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gjj7-8chj-25qp

## What is CVE-2011-5294?

CVE-2011-5294 is a medium-severity path traversal vulnerability in n/a, published on 1 Jan 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The SaveMessage method in the LEADeMail.LEADSmtp.20 ActiveX control in LTCML14n.dll 14.0.0.34 in Kofax e-Transactions Sender Sendbox 2.5.0.933 allows remote attackers to write to arbitrary files via a pathname in the first argument.

Weakness: CWE-264

## Which versions are affected by CVE-2011-5294?

It affects 1 product.


Products: Kofax Kofax E-Transactions Sender Sendbox.

## How do I fix CVE-2011-5294?

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

## Is CVE-2011-5294 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5294 and fix it if it is affected.

What it is: CVE-2011-5294 is a medium-severity path traversal vulnerability in n/a, published on 1 Jan 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-5294 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-2011-5294/ (Markdown: https://insights.sbomify.com/CVE-2011-5294/index.md)
```

## Sources

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

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