CVE-2026-42714
validatedZero produced an exploit or a check.description
Pix por Piggly for WooCommerce (pix-por-piggly) through version 2.1.2 is affected by a blind SQL injection flaw. An attacker may be able to influence database queries through vulnerable functionality; the advisory does not state the required authentication or access precondition.
mitigation
Disable the pix-por-piggly plugin where feasible, or restrict access to the affected site and WordPress functionality with network controls until a vendor-fixed release is available. Monitor the vendor for an update, as no fixed version is recorded.
outcome
Check only, differential: the check fires on the vulnerable build and is silent on the patched one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-07 10:56Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-42714
{ "etk_id": "ETK-2026-871", "cve_id": "CVE-2026-42714", "display_id": "CVE-2026-42714", "ghsa_id": null, "euvd_id": "EUVD-2026-94286", "status": "published", "anchor_state": "anchored", "title": "Blind SQL injection in Pix por Piggly for WooCommerce", "summary": "Pix por Piggly for WooCommerce (pix-por-piggly) through version 2.1.2 is affected by a blind SQL injection flaw. An attacker may be able to influence database queries through vulnerable functionality; the advisory does not state the required authentication or access precondition.", "mitigation": "Disable the pix-por-piggly plugin where feasible, or restrict access to the affected site and WordPress functionality with network controls until a vendor-fixed release is available. Monitor the vendor for an update, as no fixed version is recorded.", "vendor": "Piggly Dev", "product": "Pix por Piggly (para Woocommerce)", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 2.1.2" ], "ecosystem": null, "fixed_versions": [], "package_name": "pix-por-piggly", "purl": null } ], "cwes": [ 89 ], "cvss_score": 7.6, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L", "epss_score": 0.0023, "epss_percentile": 0.126, "epss_asof": "2026-10-21", "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 51.83902875, "t0_at": "2026-10-07T10:56:56.499000+00:00", "signals": { "check": { "at": "2026-10-07T14:05:21.702214+00:00", "days": 0.1308472594212963, "is_lower_bound": false, "measured_at": "2026-10-07T10:56:56.499000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-07T10:56:56.499000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-07T10:56:56.499000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-42714" } } }
published 2026-10-07 13:13Z
last change 2026-10-21 21:36Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.