# CVE-2016-20065: Product Catalog 8 1.2 Plugin WordPress SQL Injection

> Unauthenticated attackers can execute arbitrary SQL queries via the selectedCategory parameter to extract sensitive database information from WordPress tables.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-j9gf-hrp2-6fx3

## What is CVE-2016-20065?

CVE-2016-20065 is a high-severity SQL injection vulnerability in EvWill Product Catalog 8, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Product Catalog 8 1.2 plugin for WordPress contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the selectedCategory parameter. Attackers can submit POST requests to the admin-ajax.php endpoint with the UpdateCategoryList action to extract sensitive database information from WordPress tables.

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

## Which versions are affected by CVE-2016-20065?


## How do I fix CVE-2016-20065?

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

## Is CVE-2016-20065 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20065 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20065 and fix it if it is affected.

What it is: CVE-2016-20065 is a high-severity SQL injection vulnerability in EvWill Product Catalog 8, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20065 exists.

Affected product: EvWill Product Catalog 8. 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-2016-20065/ (Markdown: https://insights.sbomify.com/CVE-2016-20065/index.md)
```

## Sources

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

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