# CVE-2026-42714: WordPress Pix por Piggly (para Woocommerce) plugin <= 2.1.2 - SQL Injection vulnerability

> Attackers can perform blind SQL injection to read sensitive database information from the Pix por Piggly WordPress plugin.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-xjxc-jqcr-h283

## What is CVE-2026-42714?

CVE-2026-42714 is a high-severity SQL injection vulnerability in Pix por Piggly (para Woocommerce), published on 7 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Piggly Dev Pix por Piggly (para Woocommerce) pix-por-piggly allows Blind SQL Injection.This issue affects Pix por Piggly (para Woocommerce): from n/a through 2.1.2.

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

## Which versions are affected by CVE-2026-42714?


## How do I fix CVE-2026-42714?

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

## Is CVE-2026-42714 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42714 and fix it if it is affected.

What it is: CVE-2026-42714 is a high-severity SQL injection vulnerability in Pix por Piggly (para Woocommerce), published on 7 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42714 in the wild and no public exploit code.

Affected product: Pix por Piggly (para Woocommerce). 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-2026-42714/ (Markdown: https://insights.sbomify.com/CVE-2026-42714/index.md)
```

## Sources

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

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