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

> Remote attackers can execute arbitrary SQL commands via the username field in Mahara, potentially compromising database integrity and confidentiality.

- **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:** Yes
- **Published:** 7 Apr 2010
- **Updated:** 16 Sep 2024
- **Also known as:** DSA-2030-1, GHSA-7fgf-gwfr-hp5w

## What is CVE-2010-0400?

CVE-2010-0400 is a high-severity SQL injection vulnerability in Mahara Mahara, published on 7 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 lib/user.php in mahara 1.0.4 allows remote attackers to execute arbitrary SQL commands via a username.

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

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

It affects 1 product.


Products: Mahara Mahara.

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

Apply the vendor's patch.

## Is CVE-2010-0400 being exploited?

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

## Other vulnerabilities in Mahara Mahara

- [CVE-2022-45134](https://insights.sbomify.com/CVE-2022-45134/): Deserialization in n/a (critical 9.8)
- [CVE-2022-44544](https://insights.sbomify.com/CVE-2022-44544/): Command injection in n/a (critical 9.8)
- [CVE-2021-40849](https://insights.sbomify.com/CVE-2021-40849/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-1000152](https://insights.sbomify.com/CVE-2017-1000152/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-1000153](https://insights.sbomify.com/CVE-2017-1000153/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0400 is a high-severity SQL injection vulnerability in Mahara Mahara, published on 7 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-0400 in the wild and no public exploit code.

Affected product: Mahara Mahara. 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-0400/ (Markdown: https://insights.sbomify.com/CVE-2010-0400/index.md)
```

## Sources

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

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