CVE-2026-87979
MediumCVSS 5.3Summary
The Paymob for WooCommerce WordPress plugin before 4.1.14 does not verify the request signature on the card-token branch of its payment webhook. Unauthenticated attackers can write a card-token record to any user's account and enumerate registered accounts.
Risk Assessment
An attacker can associate a card token with someone else's account, potentially leading to unauthorized payments or abuse, and enumerate user accounts. The risk is high due to the nature of payment data.
Recommendation
Update the Paymob for WooCommerce plugin to version 4.1.14 or later. Check for unauthorized card token writes and consider auditing accounts.
Other vulnerabilities in Paymob for WooCommerce
See all- CVE-2026-87978Medium
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.
- CVE-2026-87981Medium
The Paymob for WooCommerce WordPress plugin before 4.1.14 does not perform a capability check on several admin AJAX actions that manage its payment-gateway configuration. Users with contributor-level access can delete, wipe, or modify that configuration, including the stored payment credentials.
- CVE-2026-66611High
Unauthenticated Cross Site Scripting (XSS) in Paymob for WooCommerce versions up to 4.1.10. An attacker can inject malicious script without authentication.
- CVE-2026-56025High
The Paymob for WooCommerce plugin version 4.1.2 and earlier contains an unauthenticated broken access control vulnerability. An attacker without authentication can exploit this flaw to gain unauthorized access to plugin functions.
Original NVD description (English source)
The Paymob for WooCommerce WordPress plugin before 4.1.14 does not verify the request signature on the card-token branch of its payment webhook, allowing unauthenticated attackers to write a card-token record to any user's account and to enumerate registered accounts.