Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-15205 – Unauthenticated SQL Injection – Paymob for WooCommerce < 4.1.9

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-15205 is an unauthenticated SQL injection vulnerability in the Paymob for WooCommerce WordPress plugin, affecting all versions before 4.1.9. The flaw resides in the plugin’s public payment callback endpoint, where a client-supplied identifier used for a "pixel lookup" is passed into a SQL query without sanitization before the payment provider’s HMAC signature is verified. The issue carries a High severity CVSS score of 8.6, as it allows remote, unauthenticated attackers to extract arbitrary data from the WordPress database.

Technical details

  • Root cause: The plugin’s Paymob callback handler builds a SQL query using a client-supplied identifier (used to look up a stored payment "pixel") without proper input sanitization.
  • Trigger condition: The vulnerable query executes before the plugin validates the HMAC signature that is meant to authenticate legitimate callback requests from Paymob, meaning no valid signature or prior authentication is required to reach the injectable code.
  • Attack vector: The callback endpoint is public-facing and unauthenticated, reachable over the network (AV:N) with low attack complexity and no user interaction.
  • Impact: Attackers can perform both in-band (reflected) and time-based blind SQL injection to read arbitrary data from the database, including user credentials and other secrets. The vulnerability affects confidentiality only (no integrity or availability impact), and the CVSS scope is "Changed."

Affected software

  • Paymob for WooCommerce (WordPress plugin) — all versions prior to 4.1.9

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Paymob for WooCommerce to version 4.1.9 or later, where the callback input is properly sanitized/validated before use in SQL queries.
  • If unable to patch immediately: Restrict or monitor access to the plugin’s payment callback endpoint at the network/WAF layer for anomalous query-string patterns and time-based request timing typical of blind SQLi, and audit database access logs for suspicious activity until the update can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge