highCVE-2026-6939

CorvusPay WooCommerce Payment Gateway <= 2.7.4 - Unauthenticated Stored Cross-Site Scripting via 'approval_code' Parameter

Q: What is affected by CVE-2026-6939?

CorvusPay WooCommerce Payment Gateway versions listed as affected should be reviewed: *-2.7.4.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

The CorvusPay WooCommerce Payment Gateway plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'approval_code' parameter in all versions up to, and including, 2.7.4 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. The unauthenticated REST endpoint POST /wp-json/corvuspay/success/ is registered with permission_callback set to __return_true, and although a signature validation step exists it only logs the result without halting execution, meaning an attacker can supply a completely arbitrary signature and have a malicious approval_code stored in the database unchallenged.

ProductCorvusPay WooCommerce Payment Gateway

CVSS7.2

EPSS0.00324

UpdatedJuly 13, 2026

Quick answer

CorvusPay WooCommerce Payment Gateway should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

*-2.7.4

Fixed versions

2.7.5

How to fix it

CorvusPay WooCommerce Payment Gateway is affected by CVE-2026-6939, a cross-site scripting issue in versions up to 2.7.4. Wordfence lists the official remediation as updating to version 2.7.5, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, WooCommerce checkout/account flows, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or vulnerable feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has CorvusPay WooCommerce Payment Gateway installed, including staging, multisite, client, and WooCommerce environments.
Confirm the installed CorvusPay WooCommerce Payment Gateway version and compare it with the affected range from the Wordfence advisory.
Update CorvusPay WooCommerce Payment Gateway to version 2.7.5, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable CorvusPay WooCommerce Payment Gateway or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review user-generated content, forms, comments, profile fields, templates, and saved plugin settings for injected scripts or unexpected HTML.
Rotate administrator sessions, API keys, webhook secrets, and integration tokens if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, and browser caches after patching so vulnerable assets or stored payloads are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the running CorvusPay WooCommerce Payment Gateway version is version 2.7.5 or newer, and record the patched version in the remediation ticket.
Verify the affected fields, forms, comments, profile data, or settings now sanitize input and escape output instead of rendering executable scripts.
Review web server, WordPress, security plugin, WAF, and application logs for exploitation attempts before and after the fix.
Retest normal user, admin, checkout, form, API, or integration workflows to confirm the update did not break expected behavior.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress WooCommerce Network Security Cross-site Scripting

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-6939?

CorvusPay WooCommerce Payment Gateway versions listed as affected should be reviewed: *-2.7.4.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.