Is CVE-2026-56029 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56029 being exploited in the wild.

How severe is CVE-2026-56029?

High severity, with a CVSS score of 7.5, published 26 June 2026.

Which products and versions are affected?

CorvusPay WooCommerce Payment Gateway <= 2.7.4.

Is there a fix for CVE-2026-56029?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-56029 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-56029?

Check whether you run CorvusPay WooCommerce Payment Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56029: CorvusPay WooCommerce Payment Gateway authentication bypass

Q: Is there a fix for CVE-2026-56029?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-56029 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-56029?

Check whether you run CorvusPay WooCommerce Payment Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-56029 · Severity: high · CVSS 7.5 · Published 2026-06-26

The CorvusPay WooCommerce Payment Gateway plugin for WordPress, which facilitates online payments for e-commerce stores, contains a security flaw that allows unauthenticated users to bypass authentication. This could allow an attacker to perform unauthorized actions that are normally restricted to high-privileged users, potentially leading to administrative access or interference with the store's operations. Business owners should update the plugin immediately to prevent unauthorized access to their site's management functions.

Technologies: CorvusPay WooCommerce Payment Gateway. Vendors: CorvusPay.

Quick answers

Is CVE-2026-56029 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56029 being exploited in the wild.
How severe is CVE-2026-56029?: High severity, with a CVSS score of 7.5, published 26 June 2026.
Which products and versions are affected?: CorvusPay WooCommerce Payment Gateway <= 2.7.4.
Is there a fix for CVE-2026-56029?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-56029 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-56029?: Check whether you run CorvusPay WooCommerce Payment Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The CorvusPay WooCommerce Payment Gateway plugin for WordPress (versions <= 2.7.4) is vulnerable to an authentication bypass via an alternate path or channel (CWE-288). The flaw allows an unauthenticated remote attacker to bypass authentication mechanisms and perform actions that should be restricted to users with higher privileges. According to the advisory, this could lead to a full administrative takeover of the WordPress site. The vulnerability is exploited over the network without requiring user interaction. A fix is available in version 2.7.5.

Affected products

CorvusPay CorvusPay WooCommerce Payment Gateway <= 2.7.4

Timeline

2026-05-08: other: Reported by ParkHyunWoo
2026-06-23: disclosed: Initial disclosure by Patchstack
2026-06-26: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.