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

> Remote attackers can execute arbitrary PHP commands and disclose server paths via the admin script in x-stat.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-24cw-v655-38cr

## What is CVE-2002-2045?

CVE-2002-2045 is a medium-severity code injection vulnerability in n/a, published on 14 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

x_stat_admin.php in x-stat 2.3 and earlier allows remote attackers to (1) execute PHP commands such as phpinfo or (2) obtain the full path of the web server via an invalid action parameter, which leaks the pathname in an error message.

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

It affects 1 product.


Products: Xqus X-Stat.

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

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

## Is CVE-2002-2045 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2044](https://insights.sbomify.com/CVE-2002-2044/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2045 is a medium-severity code injection vulnerability in n/a, published on 14 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-2045 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-2002-2045/ (Markdown: https://insights.sbomify.com/CVE-2002-2045/index.md)
```

## Sources

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

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