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

> Remote attackers can obtain the full server path by requesting a specific module when display_errors is enabled in Jupiter CMS.

- **Severity:** Low 2.6 (`AV:N/AC:H/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:** 10 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gxwf-8x9q-qwgh

## What is CVE-2006-1680?

CVE-2006-1680 is a low-severity vulnerability in n/a, published on 10 Apr 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jupiter CMS 1.1.5, when display_errors is enabled, allows remote attackers to obtain the full server path via a direct request to modules/online.php.

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

It affects 1 product.


Products: Jupiter Cms Jupiter Cms.

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

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

## Is CVE-2006-1680 being exploited?

There is no known exploitation of CVE-2006-1680 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-1680 and fix it if it is affected.

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

## Sources

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

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