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.
Metrics
Affected Vendors & Products
References
History
Fri, 14 Aug 2026 07:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-89 |
Fri, 14 Aug 2026 06:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Paymob for WooCommerce < 4.1.9 - Unauthenticated SQL Injection via Paymob Callback Pixel Lookup | |
| References |
|
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2026-08-14T06:00:11.326Z
Reserved: 2026-07-09T07:21:48.528Z
Link: CVE-2026-15205
No data.
Status : Received
Published: 2026-08-14T06:16:59.727
Modified: 2026-08-14T06:16:59.727
Link: CVE-2026-15205
No data.
OpenCVE Enrichment
Updated: 2026-08-14T07:30:17Z