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

> An attacker can perform SQL injection in the admin area of the GigPress WordPress plugin, potentially accessing or modifying database content.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-47fh-93cq-wjp3

## What is CVE-2015-9353?

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

### Official description

The gigpress plugin before 2.3.11 for WordPress has SQL injection in the admin area, a different vulnerability than CVE-2015-4066.

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

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

It affects 1 product.


Products: Tri Gigpress.

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

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

## Is CVE-2015-9353 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-0381](https://insights.sbomify.com/CVE-2023-0381/): GigPress <= 2.3.28 - Subscriber+ SQLi (high 8.8)
- [CVE-2022-4759](https://insights.sbomify.com/CVE-2022-4759/): GigPress < 2.3.28 - Contributor+ Stored XSS via Shortcode (medium 6.8)
- [CVE-2015-4066](https://insights.sbomify.com/CVE-2015-4066/): SQL injection in n/a (medium 6.5)
- [CVE-2023-7233](https://insights.sbomify.com/CVE-2023-7233/): GigPress <= 2.3.29 - Admin+ Stored Cross Site Scripting (medium 4.8)
- [CVE-2015-9354](https://insights.sbomify.com/CVE-2015-9354/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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