# CVE-2013-6936: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the tooltip parameters in the Ajaxfs plugin for MyBB.

- **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:** No
- **Published:** 4 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2f93-2pfr-964f

## What is CVE-2013-6936?

CVE-2013-6936 is a high-severity SQL injection vulnerability in n/a, published on 4 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in ajaxfs.php in the Ajax forum stat (Ajaxfs) Plugin 2.0 for MyBB (aka MyBulletinBoard) allow remote attackers to execute arbitrary SQL commands via the (1) tooltip or (2) usertooltip parameter.

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

## Which versions are affected by CVE-2013-6936?

It affects 1 product.


Products: Mybb Ajax Forum Stat.

## How do I fix CVE-2013-6936?

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

## Is CVE-2013-6936 being exploited?

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

Public exploit code:

- MyBB Ajaxfs 2 Plugin - SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6936 and fix it if it is affected.

What it is: CVE-2013-6936 is a high-severity SQL injection vulnerability in n/a, published on 4 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6936 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-2013-6936/ (Markdown: https://insights.sbomify.com/CVE-2013-6936/index.md)
```

## Sources

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

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