# CVE-2015-0919: SQL injection in n/a

> Remote administrators can execute arbitrary SQL commands in Sefrengo CMS via vulnerable parameters in the backend.

- **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:** 8 Jan 2015
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cxg5-hq83-f2jf

## What is CVE-2015-0919?

CVE-2015-0919 is a high-severity SQL injection vulnerability in n/a, published on 8 Jan 2015. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in the administrative backend in Sefrengo before 1.6.1 allow remote administrators to execute arbitrary SQL commands via the (1) idcat or (2) idclient parameter to backend/main.php.

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

## Which versions are affected by CVE-2015-0919?

It affects 1 product.


Products: Sefrengo Sefrengo.

## How do I fix CVE-2015-0919?

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

## Is CVE-2015-0919 being exploited?

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

Public exploit code:

- Sefrengo CMS 1.6.0 - SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-5052](https://insights.sbomify.com/CVE-2015-5052/): SQL injection in n/a (critical 9.8)
- [CVE-2015-1428](https://insights.sbomify.com/CVE-2015-1428/): SQL injection in n/a (high 7.5)
- [CVE-2015-0918](https://insights.sbomify.com/CVE-2015-0918/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0919 and fix it if it is affected.

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

## Sources

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

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