# CVE-2005-1510: Information disclosure in n/a

> Remote attackers can obtain sensitive path information by directly requesting the admin directory, revealing internal file paths in error messages.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fvxh-rw22-65pf

## What is CVE-2005-1510?

CVE-2005-1510 is a high-severity vulnerability in n/a, published on 11 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PwsPHP 1.2.2 allows remote attackers to obtain sensitive information via a direct request to the admin directory, which reveals the path in an error message.

## Which versions are affected by CVE-2005-1510?

It affects 1 product.


Products: Pwsphp Pwsphp.

## How do I fix CVE-2005-1510?

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

## Is CVE-2005-1510 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0942](https://insights.sbomify.com/CVE-2006-0942/): SQL injection in n/a (high 7.5)
- [CVE-2006-0943](https://insights.sbomify.com/CVE-2006-0943/): SQL injection in n/a (high 7.5)
- [CVE-2006-0668](https://insights.sbomify.com/CVE-2006-0668/): SQL injection in n/a (high 7.5)
- [CVE-2005-1509](https://insights.sbomify.com/CVE-2005-1509/): SQL injection in n/a (high 7.5)
- [CVE-2005-1511](https://insights.sbomify.com/CVE-2005-1511/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1510 and fix it if it is affected.

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

## Sources

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

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