CVE-2026-94271
validatedZero produced an exploit or a check.GHSA-hv5c-cx33-qjj9 ↗EUVD-2026-92965 ↗
description
Deema Payment Gateway for WordPress through 1.1.2 does not adequately validate payment results returned from hosted checkout. An unauthenticated attacker may cause an order to be recorded as paid without a corresponding payment, where the gateway's checkout-return handling is exposed.
mitigation
Disable the affected payment gateway or manually verify every order before fulfillment until a vendor update is available. Restrict fulfillment and reconciliation workflows so payment status is confirmed with the payment provider.
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-06 06:00Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-94271
{ "etk_id": "ETK-2026-737", "cve_id": "CVE-2026-94271", "display_id": "CVE-2026-94271", "ghsa_id": "GHSA-hv5c-cx33-qjj9", "euvd_id": "EUVD-2026-92965", "status": "published", "anchor_state": "anchored", "title": "Improper payment verification in Deema Payment Gateway", "summary": "Deema Payment Gateway for WordPress through 1.1.2 does not adequately validate payment results returned from hosted checkout. An unauthenticated attacker may cause an order to be recorded as paid without a corresponding payment, where the gateway's checkout-return handling is exposed.", "mitigation": "Disable the affected payment gateway or manually verify every order before fulfillment until a vendor update is available. Restrict fulfillment and reconciliation workflows so payment status is confirmed with the payment provider.", "vendor": null, "product": "Deema Payment Gateway", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 1.1.2" ], "ecosystem": null, "fixed_versions": [], "package_name": "Deema Payment Gateway", "purl": null } ], "cwes": [ 287 ], "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": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 20.6167033, "t0_at": "2026-10-06T06:00:20.796000+00:00", "signals": { "check": { "at": "2026-10-06T07:10:49.998914+00:00", "days": 0.04894910780092593, "is_lower_bound": false, "measured_at": "2026-10-06T06:00:20.796000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-06T06:00:20.796000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-06T06:00:20.796000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-94271" } } }
published 2026-10-06 06:50Z
last change 2026-10-21 11:52Z
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.