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

> Authenticated users can inject SQL via admin.php, or unauthenticated attackers can exploit this via CSRF to execute arbitrary SQL commands.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g7wx-w9gv-h2x2

## What is CVE-2013-3727?

CVE-2013-3727 is a high-severity SQL injection vulnerability in n/a, published on 13 Mar 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SQL injection vulnerability in Kasseler CMS before 2 r1232 allows remote authenticated users to execute arbitrary SQL commands via the groups[] parameter to admin.php.  NOTE: this can be leveraged using CSRF to allow remote unauthenticated attackers to execute arbitrary SQL commands.

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

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

It affects 1 product.


Products: Kasseler-Cms Kasseler-Cms.

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

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

## Is CVE-2013-3727 being exploited?

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

Public exploit code:

- Kasseler CMS 2 r1223 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-3729](https://insights.sbomify.com/CVE-2013-3729/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-3728](https://insights.sbomify.com/CVE-2013-3728/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3727 is a high-severity SQL injection vulnerability in n/a, published on 13 Mar 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-3727 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-2013-3727/ (Markdown: https://insights.sbomify.com/CVE-2013-3727/index.md)
```

## Sources

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

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