Quick answers
- Is CVE-2026-15205 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15205 being exploited in the wild.
- How severe is CVE-2026-15205?
- High severity, with a CVSS score of 8.6, published 14 August 2026.
- Which products and versions are affected?
- Paymob for WooCommerce before 4.1.9.
- Is there a fix for CVE-2026-15205?
- A patch was published on 2026-08-14: version 4.1.9 available Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-15205 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-15205?
- Check whether you run Paymob for WooCommerce at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an unauthenticated SQL injection in the payment callback handler (wc-api=paymob_callback). The plugin fails to sanitize the merchant_order_id (accept branch) or merchant_intention_id (flash branch) parameters before using them in a SQL query. Critically, this vulnerable query executes before HMAC signature verification, making the attack vector completely network-accessible to unauthenticated attackers. Exploitation is possible through both in-band reflection (error messages reveal query results) and time-based blind techniques (SLEEP delays confirm SQL conditions). An attacker can extract arbitrary database contents, including WordPress user credentials and configuration secrets. The vulnerability affects versions before 4.1.9; a patch is available.
Affected products
- Paymob Paymob for WooCommerce before 4.1.9
Timeline
- 2026-08-12: disclosed
- 2026-08-14: patched: version 4.1.9 available