Description
The Paymob for WooCommerce WordPress plugin before 4.1.14 does not verify the request signature on one branch of its payment webhook, allowing unauthenticated attackers to mark arbitrary WooCommerce orders as paid without any payment.
Published: 2026-09-23
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: Unauthenticated Payment Bypass
Action: Patch Now
AI Analysis

Impact

The vulnerability is present in Paymob for WooCommerce WordPress plug‑in versions prior to 4.1.14. One branch of the payment webhook fails to verify the request signature, allowing an attacker to send a forged subscription transaction callback. The attacker can set any WooCommerce order status to paid without completing a legitimate payment, creating a fraud path that can lead to revenue loss, unauthorized fulfillment of goods or services, and exploitation of the e‑commerce process. This weakness aligns with CWE‑345, an insecure or insufficient validation of cryptographic authority.

Affected Systems

Systems running the Paymob for WooCommerce plug‑in at or below version 4.1.13 are affected. No other vendors or product versions are listed. Wordpress sites that have not updated the plug‑in remain at risk.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate severity level. No EPSS score is available, so the exploitation probability is unknown, but the flaw permits unauthenticated exploitation with a low technical barrier. The vulnerability is not listed in the CISA KEV catalog. An attacker can trigger the insecure webhook simply by posting a crafted callback payload to the plugin’s endpoint; no authentication is required and the gateway does not verify the signature. Consequently, the flaw is relatively easy to exploit for those who know the webhook URL and can forge a message.

Generated by OpenCVE AI on September 23, 2026 at 14:14 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update Paymob for WooCommerce to version 4.1.14 or later.
  • Restrict inbound calls to the payment webhook endpoint, allowing only authenticated requests from Paymob’s service or by validating a known secret.
  • Review pending and paid orders for potential unauthorized status changes and correct them or re‑process the payment as needed.

Generated by OpenCVE AI on September 23, 2026 at 14:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 23 Sep 2026 11:45:00 +0000

Type Values Removed Values Added
Description The Paymob for WooCommerce WordPress plugin before 4.1.14 does not verify the request signature on one branch of its payment webhook, allowing unauthenticated attackers to mark arbitrary WooCommerce orders as paid without any payment.
Title Paymob for WooCommerce < 4.1.14 - Unauthenticated Payment Bypass via Unverified Subscription Transaction Callback
Weaknesses CWE-345
References
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'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-09-23T10:48:46.367Z

Reserved: 2026-09-09T18:30:02.460Z

Link: CVE-2026-87978

cve-icon Vulnrichment

Updated: 2026-09-23T10:33:21.971Z

cve-icon NVD

Status : Received

Published: 2026-09-23T11:17:15.880

Modified: 2026-09-23T11:17:15.880

Link: CVE-2026-87978

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-23T14:15:06Z

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity