# CVE-2007-0667: Code injection in n/a

> Remote authenticated users can execute arbitrary code via redirects in the redirect function of LedgerSMB and SQL-Ledger.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-0667, GHSA-rj2x-3668-58wh, UBUNTU-CVE-2007-0667

## What is CVE-2007-0667?

CVE-2007-0667 is a medium-severity code injection vulnerability in n/a, published on 2 Feb 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The redirect function in Form.pm for (1) LedgerSMB before 1.1.5 and (2) SQL-Ledger allows remote authenticated users to execute arbitrary code via redirects, related to callbacks, a different issue than CVE-2006-5872.

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

It affects 2 products.


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

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

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

## Is CVE-2007-0667 being exploited?

There is no known exploitation of CVE-2007-0667 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-0667 and fix it if it is affected.

What it is: CVE-2007-0667 is a medium-severity code injection vulnerability in n/a, published on 2 Feb 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0667 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-0667/ (Markdown: https://insights.sbomify.com/CVE-2007-0667/index.md)
```

## Sources

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

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