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

> Remote attackers can execute arbitrary SQL commands via the book_id parameter in info_book.asp, potentially compromising database integrity and confidentiality.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-34vq-mq3q-qr9j

## What is CVE-2007-0128?

CVE-2007-0128 is a high-severity SQL injection vulnerability in n/a, published on 9 Jan 2007. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in info_book.asp in Digirez 3.4 and earlier allows remote attackers to execute arbitrary SQL commands via the book_id parameter.

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

It affects 1 product.


Products: Digiappz Digirez.

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

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

## Is CVE-2007-0128 being exploited?

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

Public exploit code:

- DigiRez 3.4 - 'book_id' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2880](https://insights.sbomify.com/CVE-2007-2880/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0128 is a high-severity SQL injection vulnerability in n/a, published on 9 Jan 2007. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0128 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-0128/ (Markdown: https://insights.sbomify.com/CVE-2007-0128/index.md)
```

## Sources

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

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