CVE-2026-7517

Custom Payment Gateways for WooCommerce <= 2.1.0 - Unauthenticated Stored Cross-Site Scripting via 'alg_wc_cpg_input_fields' Parameter

Published Jul 1, 2026 CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Custom Payment Gateways for WooCommerce plugin is vulnerable to stored cross‑site scripting through the 'alg_wc_cpg_input_fields' parameter because input sanitization is insufficient, allowing an unauthenticated attacker to embed malicious scripts that are stored and executed whenever a checkout page is accessed. This flaw can be triggered by a crafted checkout POST request without requiring any custom input fields to be configured.

Affected Systems

WordPress installations that have the Custom Payment Gateways for WooCommerce plugin from dhruvin and are running any version up to and including 2.1.0 are affected. Versions beyond 2.1.0 are not vulnerable, but the plugin should be up‑to‑date to avoid this issue.

Risk and Exploitability

The flaw has a CVSS score of 7.2, classifying it as high severity. EPSS data is not available, so the exact likelihood of exploitation is unknown, though the vulnerability is publicly documented and can be abused by unauthenticated guests via checkout POST requests; it is not listed in the CISA KEV catalog.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Custom Payment Gateways for WooCommerce to a version newer than 2.1.0 that includes the input sanitization fix.
  • If an update is not possible, disable the custom payment gateway input fields or remove the plugin entirely to prevent exploitation.
  • Implement a web application firewall rule or enforce a content‑security policy that blocks execution of injected scripts via checkout POST requests.

Generated by OpenCVE AI on July 1, 2026 at 15:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Custom Payment Gateways for WooCommerce <= 2.1.0 - Unauthenticated Stored Cross-Site Scripting via 'alg_wc_cpg_input_fields' Parameter
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}

Subscriptions

No data.

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Jul 1, 2026, 10:32 AM
Reserved
Apr 30, 2026, 4:09 PM
Status
Deferred
Published
Jul 1, 2026, 5:16 AM
Modified
Jul 1, 2026, 1:56 PM