# CVE-2015-0898: Code injection in n/a

> Remote attackers can execute arbitrary Perl code in CGI Cafe MP Form Mail CGI eCommerce on Windows.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 21 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w9jw-49fq-4prh

## What is CVE-2015-0898?

CVE-2015-0898 is a high-severity code injection vulnerability in n/a, published on 21 Mar 2015. It can be exploited over the network.

### Official description

futomi CGI Cafe MP Form Mail CGI eCommerce before 2.0.12 on Windows allows remote attackers to execute arbitrary Perl code via unspecified vectors.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Futomi Mp Form Mail Cgi.

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

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

## Is CVE-2015-0898 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-0514](https://insights.sbomify.com/CVE-2018-0514/): Command injection in MP Form Mail CGI eCommerce Edition (critical 9.8)
- [CVE-2009-0962](https://insights.sbomify.com/CVE-2009-0962/): Privilege escalation in n/a (high 7.5)
- [CVE-2016-1212](https://insights.sbomify.com/CVE-2016-1212/): Path traversal in n/a (low 2.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-0898 is a high-severity code injection vulnerability in n/a, published on 21 Mar 2015. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2015-0898 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-0898/ (Markdown: https://insights.sbomify.com/CVE-2015-0898/index.md)
```

## Sources

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

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