# CVE-2006-4873: Information disclosure in n/a

> Remote attackers can obtain sensitive installation path information by directly requesting specific PHP module files, revealing internal server details.

- **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:** 19 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8w77-fmqm-j6fq

## What is CVE-2006-4873?

CVE-2006-4873 is a medium-severity vulnerability in n/a, published on 19 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jupiter CMS allows remote attackers to obtain sensitive information via a direct request for (1) includes/functions.php, (2) modules/register.php, (3) modules/poll.php, (4) modules/panel.php, (5) modules/pm.php, (6) modules/news.php, (7) modules/templates_change.php, (8) modules/users.php, (9) modules/misc.php, (10) modules/masspm.php, (11) modules/mass-email.php, (12) modules/main-nav.php, (13) modules/login.php, (14) modules/layout.php, (15) modules/hq.php, (16) modules/forum.php, (17) modules/forum-admin.php, (18) modules/events.php, (19) modules/emoticons.php, (20) modules/download.php, (21) modules/blocks.php, (22) modules/ban.php, (23) modules/badwords.php, (24) modules/ads.php, or (25) modules/admin.php, which reveals the installation path in various error messages.  NOTE: The modules/online.php vector is already covered by CVE-2006-1679.

## Which versions are affected by CVE-2006-4873?

It affects 1 product.


Products: Jupiter Cms Jupiter Cms.

## How do I fix CVE-2006-4873?

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

## Is CVE-2006-4873 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4428](https://insights.sbomify.com/CVE-2006-4428/): Code injection in n/a (critical 9.8)
- [CVE-2007-0971](https://insights.sbomify.com/CVE-2007-0971/): SQL injection in n/a (high 7.5)
- [CVE-2007-0972](https://insights.sbomify.com/CVE-2007-0972/): File upload in n/a (high 7.5)
- [CVE-2007-0987](https://insights.sbomify.com/CVE-2007-0987/): Path traversal in n/a (high 7.5)
- [CVE-2006-4876](https://insights.sbomify.com/CVE-2006-4876/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4873 and fix it if it is affected.

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

## Sources

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

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