CVE-2026-94270

Deema Payment Gateway <= 1.1.2 - Unauthenticated Payment Bypass and Order Manipulation via Webhook

Published Oct 6, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The Deema Payment Gateway WordPress plugin through 1.1.2 does not verify the authenticity of incoming payment provider notifications, and ships with that verification disabled by default, allowing unauthenticated attackers to mark an unpaid order as paid, or to cancel or refund an existing order.

Analysis

AI-generated

Technical impact

The Deema Payment Gateway plugin for WordPress, versions up to and including 1.1.2, fails to verify the authenticity of payment processor notifications. Because the verification mechanism is disabled by default, an attacker can send crafted webhook requests to the plugin’s endpoint and alter order status, marking an unpaid purchase as paid, canceling an order, or initiating a refund. This flaw represents missing authentication checks (CWE‑287). By manipulating transactional data, an attacker can gain financial benefit or disrupt e‑commerce operations.

Affected Systems

The only affected product is the Deema Payment Gateway WordPress plugin, versions up to and including 1.1.2. The vulnerability applies to any WordPress site that installs this plugin; no specific operating system or hosting environment is required beyond the standard WordPress stack.

Risk and Exploitability

The CVSS rating of 5.3 classifies the flaw as medium severity, while the EPSS score of less than 1 percent indicates a low probability of exploitation at this time. Nevertheless, because the vulnerability allows an unauthenticated attacker to alter financial records over the public internet, the potential impact is significant. No official resolution is documented; administrators should monitor vendor advisories for a fix or mitigate by blocking the webhook endpoint.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Deema Payment Gateway to the latest version when an official fix is released.
  • If an upgrade is not possible, enable webhook verification in the plugin settings and restrict notification sources via a shared secret or IP whitelist.
  • As a temporary measure, consider disabling webhook integration or blocking external POST requests to the notification endpoint until a patch is available.

Generated by OpenCVE AI on October 7, 2026 at 08:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions deema Payment Gateway
Vendors & Products Wordpress-extensions
Wordpress-extensions deema Payment Gateway
Type Values Removed Values Added
Weaknesses CWE-284
CWE-306
CWE-639
Type Values Removed Values Added
Weaknesses CWE-287
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-284
CWE-306
CWE-639
Type Values Removed Values Added
Description The Deema Payment Gateway WordPress plugin through 1.1.2 does not verify the authenticity of incoming payment provider notifications, and ships with that verification disabled by default, allowing unauthenticated attackers to mark an unpaid order as paid, or to cancel or refund an existing order.
Title Deema Payment Gateway <= 1.1.2 - Unauthenticated Payment Bypass and Order Manipulation via Webhook
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Oct 6, 2026, 10:41 AM
Reserved
Sep 21, 2026, 9:16 AM
Status
Deferred
Published
Oct 6, 2026, 7:16 AM
Modified
Oct 6, 2026, 3:18 PM