# CVE-2005-2723: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the username cookie in PaFileDB when cookie authentication is enabled.

- **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:** 29 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4hr3-869x-3fqh

## What is CVE-2005-2723?

CVE-2005-2723 is a high-severity SQL injection vulnerability in n/a, published on 29 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in auth.php in PaFileDB 3.1, when authmethod is set to cookies, allows remote attackers to execute arbitrary SQL commands via the username value in the pafiledbcookie cookie.

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

It affects 1 product.


Products: Php Arena Pafiledb.

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

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

## Is CVE-2005-2723 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3808](https://insights.sbomify.com/CVE-2007-3808/): SQL injection in n/a (high 7.5)
- [CVE-2005-4329](https://insights.sbomify.com/CVE-2005-4329/): SQL injection in n/a (high 7.5)
- [CVE-2005-2000](https://insights.sbomify.com/CVE-2005-2000/): SQL injection in n/a (high 7.5)
- [CVE-2005-0781](https://insights.sbomify.com/CVE-2005-0781/): SQL injection in n/a (high 7.5)
- [CVE-2005-0327](https://insights.sbomify.com/CVE-2005-0327/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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