Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-6939

HIGH · 7.2 CVSS v3.1 Published 2026-07-11

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 6 weeks old

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · high confidence

Stored XSS vulnerability in CorvusPay WooCommerce Payment Gateway plugin allows unauthenticated attackers to inject arbitrary JavaScript via the approval_code parameter through an unprotected REST endpoint (/wp-json/corvuspay/success/). The endpoint uses __return_true for permission_callback and signature validation only logs failures without blocking execution, enabling arbitrary code storage.

MitigationUpdate plugin to version beyond 2.7.4; until patch available, disable the plugin or block the vulnerable REST endpoint at the web server level.

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

CVSS breakdown

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?

dbcve checks

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

Verify CorvusPay plugin is installed

Navigate to WordPress admin > Plugins and confirm 'CorvusPay WooCommerce Payment Gateway' is installed and active, or inspect wp-content/plugins/ directory for corvuspay-woocommerce-payment-gateway folder

Affected if The plugin is installed and active
Check installed plugin version

In WordPress admin > Plugins, click on the CorvusPay plugin to view version details, or read the main plugin PHP file header for 'Version:' tag

Affected if Version is at or below the known fixed version (compare your version to the patch level)
Confirm vulnerable REST endpoint exists

Send a GET request to /wp-json/corvuspay/success/ on the site and verify the endpoint responds (even with an error)

Affected if The endpoint returns a valid REST API response, indicating the vulnerable route is registered
Check REST endpoint permission callback

Inspect the plugin source code for the REST route registration (usually in main plugin file or separate rest-api.php), look for register_rest_route calls on 'corvuspay/success' and verify permission_callback uses __return_true or no auth check

Affected if permission_callback is __return_true or missing authorization logic, allowing unauthenticated access
Verify signature validation does not block requests

Examine the plugin code handling the success endpoint - locate the signature verification logic and confirm it only logs failures via error_log or similar without returning an error or die()

Affected if Signature validation logs but does not block execution, allowing unauthenticated payload submission

User is affected if the CorvusPay WooCommerce Payment Gateway plugin is installed with a version at or below the patched release, and the vulnerable /wp-json/corvuspay/success/ REST endpoint is exposed with insufficient permission and signature validation checks.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update plugin to version beyond 2.7.4; until patch available, disable the plugin or block the vulnerable REST endpoint at the web server level.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-6939 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-6939?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.2 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 9 hrs · Moderate

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-6939 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References