# CVE-2002-1113: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in Mantis by manipulating the g_jpgraph_path parameter.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6gm6-fh7w-6j3g

## What is CVE-2002-1113?

CVE-2002-1113 is a high-severity code injection vulnerability in n/a, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

summary_graph_functions.php in Mantis 0.17.3 and earlier allows remote attackers to execute arbitrary PHP code by modifying the g_jpgraph_path parameter to reference the location of the PHP code.

## Which versions are affected by CVE-2002-1113?

It affects 1 product.


Products: Mantis Mantis.

## How do I fix CVE-2002-1113?

Upgrade to a fixed version.

## Is CVE-2002-1113 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1113 exists.

Public exploit code:

- Mantis Bug Tracker 0.15.x/0.16/0.17.x - JPGraph Remote File Inclusion Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-6515](https://insights.sbomify.com/CVE-2006-6515/): Missing authorization in n/a (critical 10.0)
- [CVE-2006-0665](https://insights.sbomify.com/CVE-2006-0665/): Other in n/a (critical 10.0)
- [CVE-2002-1110](https://insights.sbomify.com/CVE-2002-1110/): SQL injection in n/a (critical 10.0)
- [CVE-2008-4687](https://insights.sbomify.com/CVE-2008-4687/): Code injection in n/a (critical 9.0)
- [CVE-2008-4689](https://insights.sbomify.com/CVE-2008-4689/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1113 and fix it if it is affected.

What it is: CVE-2002-1113 is a high-severity code injection vulnerability in n/a, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1113 exists.

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-2002-1113/ (Markdown: https://insights.sbomify.com/CVE-2002-1113/index.md)
```

## Sources

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

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