HomeWordPress vulnerabilitiesPaymob for WooCommerce
Paymob for WooCommerce vulnerabilities
Paymob for WooCommerce has 4 known vulnerabilities in this database. The most recent published record is dated 23 Sep 2026.
- Known vulnerabilities
- 4
- Active installs
- 5,000+
- Latest version
- 4.1.14
- Last updated
- 14 Sep 2026
- Most recent
- 23 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Security weakness CVE-2026-87978 | Medium 5.3 | Before 4.1.14 | Fixed in 4.1.14 | 23 Sep 2026 |
| Broken access control CVE-2026-87979 | Medium 5.3 | Before 4.1.14 | Fixed in 4.1.14 | 23 Sep 2026 |
| Broken access control CVE-2026-87981 | Medium 4.7 | Before 4.1.14 | Fixed in 4.1.14 | 23 Sep 2026 |
| SQL injection CVE-2026-15205 | High 8.6 | Before 4.1.9 | Fixed in 4.1.9 | 14 Aug 2026 |
Read the published descriptions
- CVE-2026-87978, 23 Sep 2026
- 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 record
- CVE-2026-87979, 23 Sep 2026
- 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. CVE record
- CVE-2026-87981, 23 Sep 2026
- 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, allowing users with contributor-level access to delete, wipe, or modify that configuration, including the stored payment credentials. CVE record
- CVE-2026-15205, 14 Aug 2026
- The Paymob for WooCommerce WordPress plugin before 4.1.9 does not properly sanitise a client-supplied identifier before using it in a SQL query within its public, unauthenticated payment callback, and performs this query before verifying the payment provider's HMAC signature. This allows unauthenticated attackers to perform SQL injection and read arbitrary data from the database - including user credentials and other secrets - through both in-band (reflected) and time-based blind extraction. CVE record
What to do if you run Paymob for WooCommerce
If you run Paymob for WooCommerce, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Paymob for WooCommerce vulnerabilities
Free. We email you when a new vulnerability is published for Paymob for WooCommerce, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.