CVE-2026-92766
validatedZero produced an exploit or a check.GHSA-887q-pmvc-rpw5 ↗EUVD-2026-102824 ↗
description
Vitepos – Point of Sale (POS) for WooCommerce versions through 3.5.1 contain an SQL injection flaw in a REST API request parameter. An unauthenticated remote attacker may be able to access sensitive database information; accounts assigned a POS role can also reach the affected functionality.
mitigation
Disable the Vitepos plugin or restrict access to its REST API endpoint until the vendor provides and you deploy a corrected release. Review POS-role assignments and remove unnecessary accounts to reduce exposure.
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-16 08:27Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-92766
{ "etk_id": "ETK-2026-1883", "cve_id": "CVE-2026-92766", "display_id": "CVE-2026-92766", "ghsa_id": "GHSA-887q-pmvc-rpw5", "euvd_id": "EUVD-2026-102824", "status": "published", "anchor_state": "anchored", "title": "SQL injection in Vitepos for WooCommerce", "summary": "Vitepos – Point of Sale (POS) for WooCommerce versions through 3.5.1 contain an SQL injection flaw in a REST API request parameter. An unauthenticated remote attacker may be able to access sensitive database information; accounts assigned a POS role can also reach the affected functionality.", "mitigation": "Disable the Vitepos plugin or restrict access to its REST API endpoint until the vendor provides and you deploy a corrected release. Review POS-role assignments and remove unnecessary accounts to reduce exposure.", "vendor": "appsbd", "product": "Vitepos – Point of Sale (POS) for WooCommerce", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 3.5.1" ], "ecosystem": null, "fixed_versions": [], "package_name": "Vitepos – Point of Sale (POS) for WooCommerce", "purl": null } ], "cwes": [ 89 ], "cvss_score": 7.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "epss_score": 0.0033, "epss_percentile": 0.2463, "epss_asof": "2026-10-20", "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 44.8360005, "t0_at": "2026-10-16T08:27:42.866000+00:00", "signals": { "check": { "at": "2026-10-17T13:56:14.490427+00:00", "days": 1.2281438012384258, "is_lower_bound": false, "measured_at": "2026-10-16T08:27:42.866000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-16T08:27:42.866000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-16T08:27:42.866000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-92766" } } }
published 2026-10-17 13:11Z
last change 2026-10-21 05:31Z
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.