# CVE-2010-1359: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the coID parameter in the Direct URL module when magic_quotes_gpc is disabled.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 13 Apr 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qp79-9v76-98gj

## What is CVE-2010-1359?

CVE-2010-1359 is a medium-severity SQL injection vulnerability in n/a, published on 13 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in bluegate_seo.inc.php in the Direct URL module for xt:Commerce, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the coID parameter.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

## Which versions are affected by CVE-2010-1359?

It affects 2 products.


Products: Bluegate Direct Url, Xt-Commerce Xt-Commerce.

## How do I fix CVE-2010-1359?

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

## Is CVE-2010-1359 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1359 and fix it if it is affected.

What it is: CVE-2010-1359 is a medium-severity SQL injection vulnerability in n/a, published on 13 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-1359 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-2010-1359/ (Markdown: https://insights.sbomify.com/CVE-2010-1359/index.md)
```

## Sources

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

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