# CVE-2011-2181: SQL injection in n/a

> Remote attackers with admin privileges can execute arbitrary SQL commands via vulnerable parameters in the chat application's admin interface.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-grxg-fv5c-9v7f

## What is CVE-2011-2181?

CVE-2011-2181 is a high-severity SQL injection vulnerability in n/a, published on 29 Jun 2011. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in A Really Simple Chat (ARSC) 3.3-rc2 allow remote attackers to execute arbitrary SQL commands via the (1) arsc_user parameter to base/admin/edit_user.php, (2) arsc_layout_id parameter in base/admin/edit_layout.php, or (3) arsc_room parameter to base/admin/edit_room.php.

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

## Which versions are affected by CVE-2011-2181?

It affects 1 product.


Products: Reallysimplechat Really Simple Chat.

## How do I fix CVE-2011-2181?

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

## Is CVE-2011-2181 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2180](https://insights.sbomify.com/CVE-2011-2180/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2011-2470](https://insights.sbomify.com/CVE-2011-2470/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2181 and fix it if it is affected.

What it is: CVE-2011-2181 is a high-severity SQL injection vulnerability in n/a, published on 29 Jun 2011. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2181 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-2011-2181/ (Markdown: https://insights.sbomify.com/CVE-2011-2181/index.md)
```

## Sources

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

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