Quick answers
- Is CVE-2026-56025 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56025 being exploited in the wild.
- How severe is CVE-2026-56025?
- High severity, with a CVSS score of 7.5, published 26 June 2026.
- Which products and versions are affected?
- Paymob for WooCommerce <= 4.1.2.
- Is there a fix for CVE-2026-56025?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-56025 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-56025?
- 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 Paymob for WooCommerce plugin for WordPress suffers from a broken access control vulnerability (CWE-862) due to missing authorization checks in certain functions. This allows an unauthenticated remote attacker to execute actions that should be restricted to higher-privileged users. The vulnerability is exploitable over the network without any user interaction. While the specific impacted functions are not detailed in the advisory, the CVSS vector indicates a high impact on integrity (I:H) with no impact on confidentiality or availability. As of the advisory date, no official patch has been released.
Affected products
- Paymob Paymob for WooCommerce <= 4.1.2
Timeline
- 2026-05-06: other: Vulnerability reported by researcher Sajjad Haqi
- 2026-06-19: advisory: Initial advisory published by Patchstack
- 2026-06-26: disclosed: CVE published to NVD