# CVE-2005-2314: Auth bypass in n/a

> Remote attackers can bypass login checks to obtain administrator credentials, leading to unauthorized access and privilege escalation.

- **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:** 19 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-72m8-2j54-r5xg

## What is CVE-2005-2314?

CVE-2005-2314 is a high-severity authentication bypass vulnerability in n/a, published on 19 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

inc.login.php in PHPsFTPd 0.2 through 0.4 allows remote attackers to obtain the administrator's username and password by setting the do_login parameter and performing an edit action using user.php, which causes the login check to be bypassed and leaks the password in the response.

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

It affects 1 product.


Products: Phpsftpd Phpsftpd.

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

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

## Is CVE-2005-2314 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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