dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7517

HIGH · 7.2 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Custom Payment Gateways for WooCommerce plugin fails to sanitize the 'alg_wc_cpg_input_fields' parameter and escape it when output, allowing unauthenticated attackers to inject persistent malicious JavaScript via crafted checkout POST requests. This stored XSS executes whenever users access affected pages.

MitigationImplement proper input sanitization (sanitize_text_field and related functions) on all user-supplied parameters and output escaping (esc_html, esc_attr, esc_js) when rendering data in the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Custom Payment Gateways for WooCommerce'. Alternatively, check for the plugin directory at wp-content/plugins/payment-gateway-by-cpg/ or similar.
    Affected if The plugin is not installed, the vulnerability does not apply.
  2. Check the installed version
    In WordPress admin_plugins list, find the version number listed under the plugin name. Compare this to the affected version range if known, or check if the version predates the patch date.
    Affected if Running a version within the affected range means the vulnerability may be present.
  3. Locate the parameter handler in plugin code
    Search plugin PHP files for 'alg_wc_cpg_input_fields' using grep or a file search tool. Look in files that handle checkout POST requests, typically in includes/ or core/ directories.
    Affected if The parameter is processed by the plugin code, creating a potential attack surface.
  4. Inspect input sanitization on the parameter
    Open the file handling the parameter and verify that sanitize_text_field, sanitize_textarea_field, or similar sanitization functions are applied to $_POST['alg_wc_cpg_input_fields'] before any database storage or processing.
    Affected if No sanitization function or an inadequate function (like raw input access) is used, the vulnerability exists.
  5. Inspect output escaping before rendering
    Search for instances where the stored or processed value from 'alg_wc_cpg_input_fields' is output. Verify esc_html, esc_attr, or esc_js is applied when rendering this data in admin pages or checkout.
    Affected if The value is output without escaping functions, stored XSS is present.

If the plugin is installed and processes the alg_wc_cpg_input_fields parameter without proper sanitization on input and escaping on output, the environment is affected by this stored XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input sanitization (sanitize_text_field and related functions) on all user-supplied parameters and output escaping (esc_html, esc_attr, esc_js) when rendering data in the plugin.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7517 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data