# CVE-2026-7517: Cross-site scripting in Custom Payment Gateways for WooCommerce

> Unauthenticated attackers can inject arbitrary scripts via checkout requests, potentially leading to session hijacking or malicious actions on behalf of users.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-6q84-x2rr-737v

## What is CVE-2026-7517?

CVE-2026-7517 is a high-severity cross-site scripting vulnerability in dhruvin Custom Payment Gateways for WooCommerce, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-7517?


## How do I fix CVE-2026-7517?

No fix has been published for CVE-2026-7517 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7517 being exploited?

There is no known exploitation of CVE-2026-7517 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7517 and fix it if it is affected.

What it is: CVE-2026-7517 is a high-severity cross-site scripting vulnerability in dhruvin Custom Payment Gateways for WooCommerce, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7517 in the wild and no public exploit code.

Affected product: dhruvin Custom Payment Gateways for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7517/ (Markdown: https://insights.sbomify.com/CVE-2026-7517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7517
- OSV: https://osv.dev/vulnerability/CVE-2026-7517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7517/
Summaries are generated and may contain mistakes; the official description above is the record.