CVE-2026-7517: Custom Payment Gateways for WooCommerce (WordPress plugin) · Cross-site Scripting
Affects Custom Payment Gateways for WooCommerce (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dhruvinCustom Payment Gateways for WooCommerce | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory for updates. Until a fix is available, consider disabling or restricting use of the Custom Payment Gateways for WooCommerce plugin versions up to 2.1.0. Implementing web application firewall (WAF) rules to detect and block malicious payloads targeting the 'alg_wc_cpg_input_fields' parameter may provide temporary mitigation.
Description
The Custom Payment Gateways for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'alg_wc_cpg_input_fields' parameter in all versions up to, and including, 2.1.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is exploitable by unauthenticated guest users submitting a crafted checkout POST request, requiring no custom input fields to be configured in the plugin.
References
- wordfence.com/threat-intel/vulnerabilities/id/1defa728-9f9d-4e8f-8f6c-432c615da7f5?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-payment-gateways-woocommerce/trunk/includes/class-alg-wc-custom-payment-gateways-input-fields.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-payment-gateways-woocommerce/tags/2.1.0/includes/class-alg-wc-custom-payment-gateways-input-fields.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-payment-gateways-woocommerce/trunk/includes/class-alg-wc-custom-payment-gateways-input-fields.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-payment-gateways-woocommerce/tags/2.1.0/includes/class-alg-wc-custom-payment-gateways-input-fields.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-payment-gateways-woocommerce/trunk/includes/class-alg-wc-custom-payment-gateways-input-fields.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/custom-payment-gateways-woocommerce/tags/2.1.0/includes/class-alg-wc-custom-payment-gateways-input-fields.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3578163%40custom-payment-gateways-woocommerce&new=3578163%40custom-payment-gateways-woocommerce&sfp_email=&sfph_mail= (opens in a new tab)