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

> SQL injection in the awesome-filterable-portfolio WordPress plugin allows attackers to manipulate database queries via the item_id parameter.

- **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:** 10 Oct 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-834v-68v2-5mqq

## What is CVE-2015-9461?

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

### Official description

The awesome-filterable-portfolio plugin before 1.9 for WordPress has afp_get_new_portfolio_item_page SQL injection via the item_id parameter.

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

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

It affects 1 product.


Products: Brinidesigner Awesome Filterable Portfolio.

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

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

## Is CVE-2015-9461 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-35238](https://insights.sbomify.com/CVE-2022-35238/): WordPress Awesome Filterable Portfolio plugin <= 1.9.7 - Unauthenticated Plugin Settings Change vulnerability (medium 6.5)
- [CVE-2022-40193](https://insights.sbomify.com/CVE-2022-40193/): Cross-site scripting in Awesome Filterable Portfolio (WordPress plugin) (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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