# CVE-2006-2128: Multiple SQL injection vulnerabilities in Pro Publish 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) email and (2)


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x76j-ww65-vj9g

## What is CVE-2006-2128?

CVE-2006-2128 is a high-severity vulnerability in n/a, published on 1 May 2006. 

### Official description

Multiple SQL injection vulnerabilities in Pro Publish 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) email and (2) password parameter to (a) admin/login.php, (3) find_str parameter to (b) search.php, or (4) artid parameter to (c) art.php, or (5) catid parameter to (d) cat.php.

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

## Which versions are affected by CVE-2006-2128?

It affects 1 product.


Products: Deltascripts Pro Publish.

## How do I fix CVE-2006-2128?

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

## Is CVE-2006-2128 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2821](https://insights.sbomify.com/CVE-2006-2821/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2006-2129](https://insights.sbomify.com/CVE-2006-2129/): Direct static code injection vulnerability in Pro Publish 2.0 allows remote authenticated administrators to execute arbitrary PHP code by ed (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2128 and fix it if it is affected.

What it is: CVE-2006-2128 is a high-severity vulnerability in n/a, published on 1 May 2006. 
Exploitation: There is no known exploitation of CVE-2006-2128 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-2006-2128/ (Markdown: https://insights.sbomify.com/CVE-2006-2128/index.md)
```

## Sources

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

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