# CVE-2015-9352: The wp-polls plugin before 2.72 for WordPress has SQL injection.


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Aug 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g563-whvv-c886

## What is CVE-2015-9352?

CVE-2015-9352 is a critical vulnerability in n/a, published on 27 Aug 2019. 

### Official description

The wp-polls plugin before 2.72 for WordPress has SQL injection.

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

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

It affects 1 product.


Products: Wp-Polls Project Wp-Polls.

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

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

## Is CVE-2015-9352 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10936](https://insights.sbomify.com/CVE-2016-10936/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-13426](https://insights.sbomify.com/CVE-2024-13426/): WP-Polls <= 2.77.2 - Unauthenticated SQL Injection to Stored Cross-Site Scripting (medium 5.4)
- [CVE-2022-1581](https://insights.sbomify.com/CVE-2022-1581/): WP-Polls < 2.76.0 - IP Validation Bypass (medium 5.3)
- [CVE-2022-40130](https://insights.sbomify.com/CVE-2022-40130/): WordPress WP-Polls plugin <= 2.76.0 - Auth. Race Condition vulnerability (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-9352 is a critical vulnerability in n/a, published on 27 Aug 2019. 
Exploitation: There is no known exploitation of CVE-2015-9352 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-9352/ (Markdown: https://insights.sbomify.com/CVE-2015-9352/index.md)
```

## Sources

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

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