# CVE-2007-3193: Auth bypass in n/a

> Remote attackers can bypass authentication in PhpWiki by using an empty password if the minimum password length configuration is not set.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qqr6-7wx3-g97v

## What is CVE-2007-3193?

CVE-2007-3193 is a critical authentication bypass vulnerability in n/a, published on 12 Jun 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

lib/WikiUser/LDAP.php in PhpWiki before 1.3.13p1, when the configuration lacks a nonzero PASSWORD_LENGTH_MINIMUM, might allow remote attackers to bypass authentication via an empty password, which causes ldap_bind to return true when used with certain LDAP implementations.

## Which versions are affected by CVE-2007-3193?

It affects 1 product.


Products: Phpwiki Phpwiki.

## How do I fix CVE-2007-3193?

Upgrade to a fixed version.

## Is CVE-2007-3193 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2025](https://insights.sbomify.com/CVE-2007-2025/): File upload in n/a (high 7.5)
- [CVE-2007-2024](https://insights.sbomify.com/CVE-2007-2024/): File upload in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3193 and fix it if it is affected.

What it is: CVE-2007-3193 is a critical authentication bypass vulnerability in n/a, published on 12 Jun 2007. 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-2007-3193 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-2007-3193/ (Markdown: https://insights.sbomify.com/CVE-2007-3193/index.md)
```

## Sources

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

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