Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-56029 – Authentication Bypass – CorvusPay WooCommerce Payment Gateway <= 2.7.4

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-56029 is a high-severity unauthenticated authentication bypass vulnerability (CWE-288: Authentication Bypass Using an Alternate Path or Channel) in the CorvusPay WooCommerce Payment Gateway WordPress plugin, affecting all versions up to and including 2.7.4. With a CVSS 3.1 base score of 7.5, the flaw allows unauthenticated remote attackers to bypass payment callback authentication with no credentials, no complexity, and no user interaction required, posing a direct threat to the integrity of order and payment processing on affected WooCommerce stores. A patched version (2.7.5) has been released and immediate upgrading is strongly recommended.

Technical details

  • Root cause: Insufficient signature validation on CorvusPay payment callback requests, classified as CWE-288 (Authentication Bypass Using an Alternate Path or Channel). The fix introduced in version 2.7.5 explicitly adds "signature validation for CorvusPay success and cancel callback requests," confirming that prior versions lacked proper cryptographic verification of inbound callback payloads.
  • Trigger conditions: An unauthenticated attacker sends a crafted HTTP request to the plugin’s payment callback endpoint (success or cancel), bypassing the authentication mechanism without valid credentials or session context.
  • Attack vector: Network-accessible (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction needed (UI:N) — exploitable remotely by any unauthenticated actor.
  • Impact: High integrity impact (I:H) with no confidentiality or availability impact. Successful exploitation enables unauthenticated manipulation of payment callbacks, including the ability to mark orders as successfully completed without actual payment being processed, directly undermining the financial controls of affected WooCommerce stores.

Affected software

  • CorvusPay WooCommerce Payment Gateway (WordPress plugin: corvuspay-woocommerce-integration) — all versions <= 2.7.4

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Mitigation and recommended actions

  • Immediate: Update the CorvusPay WooCommerce Payment Gateway plugin to version 2.7.5 or later via the WordPress admin dashboard or WordPress.org. Version 2.7.5 introduces signature validation for payment callback requests and explicitly addresses unauthorized order completion.
  • If immediate patching is not feasible: Temporarily disable the CorvusPay plugin and switch to an alternative payment method until the update can be safely applied. Additionally, review recent order history for any anomalous "completed" or "paid" orders that did not correspond to confirmed payment transactions.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge