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

> Remote attackers can obtain the installation path via error messages in view_album.php, exposing sensitive server information.

- **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 May 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gcr6-f25q-5p9w

## What is CVE-2006-2463?

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

### Official description

view_album.php in SelectaPix 1.31 and earlier allows remote attackers to obtain the installation path via a certain request, which displays the path in an error message, possibly due to an invalid or missing parameter.

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

It affects 1 product.


Products: Out of the Trees Web Design Selectapix.

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

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

## Is CVE-2006-2463 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2912](https://insights.sbomify.com/CVE-2006-2912/): SQL injection in n/a (high 7.5)
- [CVE-2006-2722](https://insights.sbomify.com/CVE-2006-2722/): SQL injection in n/a (high 7.5)
- [CVE-2006-2913](https://insights.sbomify.com/CVE-2006-2913/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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