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

> Remote attackers can bypass authentication in PHP Easy Download via edit.php, gaining unauthorized access to protected features.

- **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:** 21 Nov 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2g69-fwvg-7wfv

## What is CVE-2005-3698?

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

### Official description

PHP Easy Download allows remote attackers to bypass authentication via edit.php.

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

It affects 1 product.


Products: Php Easy Download Php Easy Download.

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

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

## Is CVE-2005-3698 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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