CVE-2026-84169
validatedZero produced an exploit or a check.GHSA-vjc6-47gr-qc78 ↗EUVD-2026-92260 ↗
description
UPI QR Code Payment Gateway for WordPress through 1.4.3 can accept payment confirmations without properly tying them to the relevant order and customer. An unauthenticated attacker may be able to cause arbitrary orders to be recorded as paid without completing payment when the confirmation functionality is exposed.
mitigation
Disable or remove the affected plugin until the vendor provides an update. If operationally possible, restrict public access to its payment-confirmation functionality and manually verify order payments.
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-05 06:00Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-84169
{ "etk_id": "ETK-2026-628", "cve_id": "CVE-2026-84169", "display_id": "CVE-2026-84169", "ghsa_id": "GHSA-vjc6-47gr-qc78", "euvd_id": "EUVD-2026-92260", "status": "published", "anchor_state": "anchored", "title": "Payment confirmation authorization flaw in UPI QR Code Payment Gateway", "summary": "UPI QR Code Payment Gateway for WordPress through 1.4.3 can accept payment confirmations without properly tying them to the relevant order and customer. An unauthenticated attacker may be able to cause arbitrary orders to be recorded as paid without completing payment when the confirmation functionality is exposed.", "mitigation": "Disable or remove the affected plugin until the vendor provides an update. If operationally possible, restrict public access to its payment-confirmation functionality and manually verify order payments.", "vendor": null, "product": "UPI QR Code Payment Gateway", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 1.4.3" ], "ecosystem": null, "fixed_versions": [], "package_name": "UPI QR Code Payment Gateway", "purl": null } ], "cwes": [ 639 ], "cvss_score": 5.3, "cvss_src": "nvd", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "epss_score": 0.0018, "epss_percentile": 0.073, "epss_asof": "2026-10-20", "automation": "deterministic", "check": true, "check_confidence_basis": "differential", "exploit": false, "pipeline_minutes": 53.471450983333334, "t0_at": "2026-10-05T06:00:23.456000+00:00", "signals": { "check": { "at": "2026-10-05T09:29:27.920978+00:00", "days": 0.145190566875, "is_lower_bound": false, "measured_at": "2026-10-05T06:00:23.456000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-05T06:00:23.456000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-05T06:00:23.456000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-84169" } } }
published 2026-10-05 06:45Z
last change 2026-10-21 06:34Z
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.