# CVE-2014-8728: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the login page, potentially accessing or modifying sensitive fraud management data.

- **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:** 2 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fvqj-jqjq-6m5w

## What is CVE-2014-8728?

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

### Official description

SQL injection vulnerability in the login page (login/login) in Subex ROC Fraud Management (aka Fraud Management System and FMS) 7.4 and earlier allows remote attackers to execute arbitrary SQL commands via the ranger_user[name] parameter.

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

## Which versions are affected by CVE-2014-8728?

It affects 1 product.


Products: Subex Roc Fraud Management System.

## How do I fix CVE-2014-8728?

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

## Is CVE-2014-8728 being exploited?

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

Public exploit code:

- Subex Fms 7.4 - SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8728 and fix it if it is affected.

What it is: CVE-2014-8728 is a high-severity SQL injection vulnerability in n/a, published on 2 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8728 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-2014-8728/ (Markdown: https://insights.sbomify.com/CVE-2014-8728/index.md)
```

## Sources

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

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