# CVE-2007-6375: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via vulnerable parameters in Bitweaver, potentially accessing or modifying database contents.

- **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:** 15 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8mhm-fj7c-2cf8

## What is CVE-2007-6375?

CVE-2007-6375 is a high-severity SQL injection vulnerability in n/a, published on 15 Dec 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in Bitweaver 2.0.0 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) sort_mode parameter to wiki/list_pages.php and the (2) highlight parameter to search/index.php.  NOTE: the researcher also reported injection via JavaScript code in the Search box, but this is probably a forced SQL error or other separate primary issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Bitweaver Bitweaver.

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

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

## Is CVE-2007-6375 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6375 exists.

Public exploit code:

- Bitweaver 1.x/2.0 - '/search/index.php?highlight' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-1678](https://insights.sbomify.com/CVE-2009-1678/): Path traversal in n/a (high 7.5)
- [CVE-2006-6923](https://insights.sbomify.com/CVE-2006-6923/): SQL injection in n/a (high 7.5)
- [CVE-2005-4380](https://insights.sbomify.com/CVE-2005-4380/): SQL injection in n/a (high 7.5)
- [CVE-2007-6412](https://insights.sbomify.com/CVE-2007-6412/): Code injection in n/a (medium 6.8)
- [CVE-2006-6925](https://insights.sbomify.com/CVE-2006-6925/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6375 is a high-severity SQL injection vulnerability in n/a, published on 15 Dec 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6375 exists.

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-6375/ (Markdown: https://insights.sbomify.com/CVE-2007-6375/index.md)
```

## Sources

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

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