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

> Remote attackers can bypass authentication in SQL-Ledger admin.pl to gain unauthorized access without valid credentials.

- **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:** Yes
- **Published:** 13 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-1436, GHSA-pg5m-33gp-3g8h

## What is CVE-2007-1436?

CVE-2007-1436 is a high-severity authentication bypass vulnerability in n/a, published on 13 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in admin.pl in SQL-Ledger before 2.6.26 and LedgerSMB before 1.1.9 allows remote attackers to bypass authentication via unknown vectors that prevents a password check from occurring.

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

It affects 2 products.


Products: Ledgersmb Ledgersmb, Sql-Ledger Sql-Ledger.

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

Upgrade to a fixed version.

## Is CVE-2007-1436 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3907](https://insights.sbomify.com/CVE-2007-3907/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-1329](https://insights.sbomify.com/CVE-2007-1329/): Path traversal in n/a (critical 10.0)
- [CVE-2018-9246](https://insights.sbomify.com/CVE-2018-9246/): Command injection in n/a (critical 9.8)
- [CVE-2007-1437](https://insights.sbomify.com/CVE-2007-1437/): Auth bypass in n/a (critical 9.0)
- [CVE-2008-4077](https://insights.sbomify.com/CVE-2008-4077/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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