Quick answers
- Is CVE-2026-66611 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66611 being exploited in the wild.
- How severe is CVE-2026-66611?
- High severity, with a CVSS score of 7.1, published 20 August 2026.
- Which products and versions are affected?
- Paymob for WooCommerce <=4.1.10.
- Is there a fix for CVE-2026-66611?
- A patch was published on 2026-08-19: Version 4.1.11 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66611 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-66611?
- Check whether you run Paymob for WooCommerce at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stored or reflected cross-site scripting (XSS) flaw in Paymob for WooCommerce versions up to 4.1.10 that does not properly sanitize user-supplied input. An unauthenticated attacker can craft a malicious payload and inject it into vulnerable parameters, which are then executed in the victim's browser without proper escaping or validation. The attack requires user interaction—such as clicking a malicious link or visiting a crafted page—to trigger the payload. Successful exploitation allows the attacker to steal authentication cookies, session tokens, or sensitive payment information. The vulnerability was patched in version 4.1.11 and users should update immediately to mitigate risk.
Affected products
- Paymob Paymob for WooCommerce <=4.1.10
Timeline
- 2026-08-20: disclosed
- 2026-08-19: patched: Version 4.1.11 released