# CVE-2007-3002: Information disclosure in n/a

> Remote attackers can obtain sensitive path information via invalid parameters in PHP JackKnife error messages.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 4 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f6x6-3cm4-fjmc

## What is CVE-2007-3002?

CVE-2007-3002 is a medium-severity vulnerability in n/a, published on 4 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PHP JackKnife (PHPJK) allows remote attackers to obtain sensitive information via (1) a request to index.php with an invalid value of the iParentUnq[] parameter, or a request to G_Display.php with an invalid (2) iCategoryUnq[] or (3) sSort[] array parameter, which reveals the path in various error messages.

## Which versions are affected by CVE-2007-3002?

It affects 1 product.


Products: Php Jackknife Php Jackknife.

## How do I fix CVE-2007-3002?

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

## Is CVE-2007-3002 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3000](https://insights.sbomify.com/CVE-2007-3000/): SQL injection in n/a (high 7.5)
- [CVE-2007-3001](https://insights.sbomify.com/CVE-2007-3001/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-4239](https://insights.sbomify.com/CVE-2005-4239/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3002 and fix it if it is affected.

What it is: CVE-2007-3002 is a medium-severity vulnerability in n/a, published on 4 Jun 2007. 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-2007-3002 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-2007-3002/ (Markdown: https://insights.sbomify.com/CVE-2007-3002/index.md)
```

## Sources

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

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