CVE-2026-15205
Unauthenticated SQL injection in Paymob for WooCommerce payment callback.
Is CVE-2026-15205 being exploited?
Not confirmed. CVE-2026-15205 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-15205?
CVE-2026-15205 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-15205?
Yes. A fix has been recorded for CVE-2026-15205. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15205 affect?
CVE-2026-15205 affects Paymob for WooCommerce (versions <4.1.9), WordPress sites using the plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15205?
Update Paymob to 4.1.9+, ensure HMAC verification occurs before DB queries, audit/rotate secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQL injection in public payment callback (before HMAC check) enabling data exfiltration including user credentials and secrets.
Immediate action required
- affected< 4.1.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.