# CVE-2008-1591: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via HTTP headers when magic_quotes_runtime is enabled, compromising database integrity.

- **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:** 31 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fmhx-g7fq-9624

## What is CVE-2008-1591?

CVE-2008-1591 is a high-severity SQL injection vulnerability in n/a, published on 31 Mar 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The pnVarPrepForStore function in PostNuke 0.764 and earlier skips input sanitization when magic_quotes_runtime is enabled, which allows remote attackers to conduct SQL injection attacks and execute arbitrary SQL commands via input associated with server variables, as demonstrated by the CLIENT_IP HTTP header (HTTP_CLIENT_IP variable).

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

## Which versions are affected by CVE-2008-1591?

It affects 1 product.


Products: Postnuke Postnuke.

## How do I fix CVE-2008-1591?

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

## Is CVE-2008-1591 being exploited?

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

Public exploit code:

- PostNuke 0.764 - Blind SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-1713](https://insights.sbomify.com/CVE-2010-1713/): SQL injection in n/a (high 7.5)
- [CVE-2005-1697](https://insights.sbomify.com/CVE-2005-1697/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-1698](https://insights.sbomify.com/CVE-2005-1698/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1591 and fix it if it is affected.

What it is: CVE-2008-1591 is a high-severity SQL injection vulnerability in n/a, published on 31 Mar 2008. 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-2008-1591 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-2008-1591/ (Markdown: https://insights.sbomify.com/CVE-2008-1591/index.md)
```

## Sources

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

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