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

> Remote attackers can execute arbitrary SQL commands via a crafted cookie in Collabtive, potentially accessing or modifying database contents.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mjch-7g5x-p6j8

## What is CVE-2010-4269?

CVE-2010-4269 is a high-severity SQL injection vulnerability in n/a, published on 16 Nov 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in managechat.php in Collabtive 0.65 allows remote attackers to execute arbitrary SQL commands via the chatstart[USERTOID] cookie in a pull action.

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

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

It affects 1 product.


Products: O-Dyn Collabtive.

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

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

## Is CVE-2010-4269 being exploited?

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

Public exploit code:

- Collabtive 0.65 - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-5027](https://insights.sbomify.com/CVE-2013-5027/): Missing authorization in n/a (critical 9.8)
- [CVE-2010-5285](https://insights.sbomify.com/CVE-2010-5285/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-3246](https://insights.sbomify.com/CVE-2014-3246/): SQL injection in n/a (medium 6.5)
- [CVE-2013-6872](https://insights.sbomify.com/CVE-2013-6872/): SQL injection in n/a (medium 6.5)
- [CVE-2012-2670](https://insights.sbomify.com/CVE-2012-2670/): File upload in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-4269 is a high-severity SQL injection vulnerability in n/a, published on 16 Nov 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-4269 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-4269/ (Markdown: https://insights.sbomify.com/CVE-2010-4269/index.md)
```

## Sources

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

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