# CVE-2001-1226: SQL injection in n/a

> Remote attackers can modify SQL queries in AdCycle due to improper input sanitization, allowing unauthorized data access or modification.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-23cx-5wrj-f57f

## What is CVE-2001-1226?

CVE-2001-1226 is a medium-severity SQL injection vulnerability in n/a, published on 15 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AdCycle 1.17 and earlier allow remote attackers to modify SQL queries, which are not properly sanitized before being passed to the MySQL database.

## Which versions are affected by CVE-2001-1226?

It affects 1 product.


Products: Adcycle Adcycle.

## How do I fix CVE-2001-1226?

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

## Is CVE-2001-1226 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1053](https://insights.sbomify.com/CVE-2001-1053/): SQL injection in n/a (critical 10.0)
- [CVE-2001-0425](https://insights.sbomify.com/CVE-2001-0425/): SQL injection in n/a (high 7.5)
- [CVE-2000-1161](https://insights.sbomify.com/CVE-2000-1161/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1226 and fix it if it is affected.

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

## Sources

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

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