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

> Authenticated admin or teacher users can execute arbitrary SQL commands via the iotask module in DoceboLMS.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/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:** 30 Aug 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-77jf-38wv-64j5

## What is CVE-2011-5135?

CVE-2011-5135 is a medium-severity SQL injection vulnerability in n/a, published on 30 Aug 2012. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in the save_connection function in lib/lib.iotask.php in the iotask module in DoceboLMS 4.0.4 and earlier allow remote authenticated users with admin or teacher privileges to execute arbitrary SQL commands via the (1) coursereportuiconfig[name] or (2) coursereportuiconfig[description] parameters to index.php.

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

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

It affects 1 product.


Products: Docebo Docebolms.

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

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

## Is CVE-2011-5135 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-5135 exists.

Public exploit code:

- Docebo Lms 4.0.4 - 'Messages' Remote Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-3726](https://insights.sbomify.com/CVE-2011-3726/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-5135 is a medium-severity SQL injection vulnerability in n/a, published on 30 Aug 2012. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-5135 exists.

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-5135/ (Markdown: https://insights.sbomify.com/CVE-2011-5135/index.md)
```

## Sources

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

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