# CVE-2008-7075: Multiple SQL injection vulnerabilities in Kalptaru Infotech Ltd.


- **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:** 25 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f39v-mvgv-mqg2

## What is CVE-2008-7075?

CVE-2008-7075 is a high-severity vulnerability in n/a, published on 25 Aug 2009. 

### Official description

Multiple SQL injection vulnerabilities in Kalptaru Infotech Ltd. Star Articles 6.0 allow remote attackers to inject arbitrary SQL commands via (1) the subcatid parameter to article.list.php; or the artid parameter to (2) article.print.php, (3) article.comments.php, (4) article.publisher.php, or (5) article.download.php; and (6) the PATH_INFO to article.download.php.  NOTE: some of these details are obtained from third party information.

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

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

It affects 1 product.


Products: Kalptaru Infotech Stararticles.

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

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

## Is CVE-2008-7075 being exploited?

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

Public exploit code:

- Star Articles 6.0 - Blind SQL Injection (1) (exploitdb)
- Star Articles 6.0 - Blind SQL Injection (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-7076](https://insights.sbomify.com/CVE-2008-7076/): File upload in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7075 is a high-severity vulnerability in n/a, published on 25 Aug 2009. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-7075 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-7075/ (Markdown: https://insights.sbomify.com/CVE-2008-7075/index.md)
```

## Sources

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

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