CVE-2026-15205
A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.
Detection and validation
Mapped metadata availability only. These signals do not change priority.
Sigma
Not mapped by tracked sources.
Atomic
Not mapped by tracked sources.
Nuclei
Not mapped by tracked sources.
What it is
ReportedThe 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. Source description excerpt; complete tracked detail loads below.
Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:
What is affected
ReportedPaymob; Paymob for WooCommerce. Product-level identification only; no affected-version conclusion is available from this field.
Source reported · Source: NVD · Source last published: · Source last updated: · Tracker data as of:
Urgency and basis
ReportedAct · 440.7
Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:
Exploitation evidence
Reportedlisted by a tracked exploitation catalog · VulnCheck KEV
Source reported · VulnCheck KEV added: · Source last updated: · Tracker data as of:
What to do
ReportedApply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:
Evidence detail
Loading the full tracker evidence record…