CVE-2026-15205

HIGHPre-NVD 8.68.6—
EchelonGraph scoreHIGH confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-14. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(high)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 14, 2026

Last Modified

August 14, 2026

Advisory Details (1)

Auto-updated Aug 14, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Paymob for WooCommerce < 4.1.9 – Unauthenticated SQL Injection via Paymob Callback Pixel Lookup | CVE 2026-15205 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/cbde48bb-5aa4-4f69-8101-095132239923/

Vendor Advisories for CVE-2026-15205(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 31× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:06 UTCGHSA enrichment
  3. 2026-08-20 10:35 UTCGHSA enrichment
  4. 2026-08-19 23:07 UTCEG score recompute
  5. 2026-08-19 23:07 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 11:38 UTCGHSA enrichment
  8. 2026-08-19 00:10 UTCEG score recompute
  9. 2026-08-19 00:10 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 12:41 UTCGHSA enrichment
  12. 2026-08-18 00:47 UTCEG score recompute
  13. 2026-08-18 00:47 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 13:15 UTCGHSA enrichment
  16. 2026-08-17 01:48 UTCEG score recompute
  17. 2026-08-17 01:48 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:20 UTCGHSA enrichment
  20. 2026-08-16 02:53 UTCEG score recompute
  21. 2026-08-16 02:53 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 15:26 UTCGHSA enrichment
  24. 2026-08-15 03:59 UTCEG score recompute
  25. 2026-08-15 03:59 UTCGHSA enrichment
Show 8 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 16:31 UTCGHSA enrichment
  3. 2026-08-14 16:04 UTCEG score recompute▲ 8.60
  4. 2026-08-14 16:04 UTCGHSA enrichment
  5. 2026-08-14 16:03 UTCMITRE cvelistV5CVSS v3 → 8.6 · severity → HIGH
  6. 2026-08-14 06:26 UTCNVD update
  7. 2026-08-14 06:09 UTCEG score recompute
  8. 2026-08-14 06:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15205?
CVE-2026-15205 is a high vulnerability published on August 14, 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…
When was CVE-2026-15205 disclosed?
CVE-2026-15205 was first published in the National Vulnerability Database on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15205 actively exploited?
CVE-2026-15205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.6% of all scored CVEs.
What is the CVSS score of CVE-2026-15205?
CVE-2026-15205 has a CVSS v3.1 base score of 8.6 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-15205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15205, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15205

Explore →

Is Your Infrastructure Affected by CVE-2026-15205?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs