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

> Remote attackers can execute arbitrary SQL commands via the create parameter, potentially leading to code execution or data theft.

- **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 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rgqg-rv88-c9g3

## What is CVE-2014-9445?

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

### Official description

SQL injection vulnerability in incl/create.inc.php in Installatron GQ File Manager 0.2.5 allows remote attackers to execute arbitrary SQL commands via the create parameter to index.php.  NOTE: this can be leveraged for cross-site scripting (XSS) attacks by creating a file that generates an error.  NOTE: this issue was originally incorrectly mapped to CVE-2014-1137; see CVE-2014-1137 for more information.

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

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

It affects 1 product.


Products: Installatron Gatequest File Manager.

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

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

## Is CVE-2014-9445 being exploited?

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

Public exploit code:

- GQ File Manager 0.2.5 - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9445 is a high-severity SQL injection vulnerability in n/a, published on 2 Jan 2015. 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-9445 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-9445/ (Markdown: https://insights.sbomify.com/CVE-2014-9445/index.md)
```

## Sources

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

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