Vulnerability · CVE-2026-15205
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Published Aug 14, 2026 · corrected/updated Aug 14, 2026 · Paymob Paymob for WooCommerce · evidence confidence very high
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.
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-15205 is a unknown public vulnerability record for Paymob Paymob for WooCommerce. CISA lists it as known exploited. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether Paymob Paymob for WooCommerce is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: Paymob Paymob for WooCommerce. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: EPSS 0.4%. CISA lists it as known exploited. Sources contributing to this record: cve_org, epss, vulncheck_kev. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Confirmed in CISA KEV since Aug 14, 2026. Listed in CISA KEV and VulnCheck KEV.
Patch and remediation
Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Aug 14, 2026 · VulnCheck KEV
Detected
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 c
Aug 14, 2026 · CISA KEV
Known exploited
Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected
- vendor Paymob Paymob for WooCommerceversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2026-15205
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-15205
30-day exploitation probability 0.4%
first.org - VulnCheck KEVConfirmed exploitationCVE-2026-15205
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. Thi
vulncheck.com