Skip to main content

CorvusPay WooCommerce CVE-2026-56029

| EUVDEUVD-2026-39692 HIGH
Authentication Bypass Using an Alternate Path or Channel (CWE-288)
2026-06-26 audit@patchstack.com GHSA-4jhm-9928-rqx4
7.5
CVSS 3.1 · Vendor: patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify store using CorvusPay plugin
  2. Delivery
    Send crafted request to callback endpoint
  3. Exploit
    Bypass authentication check (CWE-288)
  4. Execution
    Forge trusted payment/order state
  5. Impact
    Unauthorized integrity change without payment

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
Exploitation Conditions

Exploitation requires only that a reachable WordPress site runs the CorvusPay WooCommerce Payment Gateway plugin at version 2.7.4 or earlier with its checkout/callback endpoints network-accessible - per AV:N/AC:L/PR:N/UI:N there is no authentication, no user interaction, and no special access needed against such an installation. The concrete prerequisite is presence and activation of the vulnerable plugin handling payment flows; the practical limiting factors are that the store must actually have this specific (relatively niche) gateway installed and the affected endpoint must be internet-reachable, which bounds the population of exploitable targets even though no per-target configuration toggle is required.

Impact

Signals are mixed and partly conflicting, which should temper prioritization. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, I:H) describes a network-reachable, low-complexity, unauthenticated integrity attack - a genuinely high-exposure profile that justifies the 7.5 base score. However, no EPSS probability is provided, the CVE is not in CISA KEV, and no POC is referenced, so there is no evidence of active or imminent exploitation; treat real-world risk as moderate and dependent on exposure of a vulnerable store. A notable inconsistency: Patchstack's tag labels this 'Information Disclosure,' yet the CVSS vector sets C:N and I:H - verify with the vendor whether the true impact is confidentiality or integrity, as this changes both detection and remediation focus. Net: a legitimate patch-soon issue for sites running this plugin, but not an emergency without exposure confirmation or exploitation signal.

Exploit ScenarioDerived

An attacker who knows a target WooCommerce store uses the CorvusPay plugin sends a crafted unauthenticated HTTP request to the plugin's exposed payment/callback handler, exploiting the missing authentication check to alter trusted order or integration state - for example forging a successful-payment confirmation to obtain goods without paying. The attack requires only network access and low complexity (AV:N/AC:L/PR:N/UI:N) and no victim interaction; no public POC is currently identified, which modestly raises the effort to weaponize.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 26, 2026

Authentication bypass in the CorvusPay WooCommerce Payment Gateway plugin for WordPress (versions 2.7.4 and earlier) lets unauthenticated remote attackers manipulate the payment/integration workflow without valid credentials, per the CVSS 3.1 vector (AV:N/PR:N) and CWE-288. The flaw scores 7.5 with integrity impact only (I:H, C:N, A:N), meaning an attacker can tamper with trusted state - most plausibly forging payment confirmation/callback validation - rather than steal data or take a site down. No public exploit is identified at time of analysis and the issue is not listed in CISA KEV.

RemediationAI

No exact fixed version is provided in the supplied data, so the patched build cannot be independently confirmed here; consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/corvuspay-woocommerce-integration/vulnerability/wordpress-corvuspay-woocommerce-payment-gateway-plugin-2-7-4-broken-authentication-vulnerability?_s_id=cve) for the vendor's fixed release and upgrade beyond 2.7.4 as soon as it is published. Until a patched version is applied, the most effective compensating control is to place the vulnerable plugin's callback/return endpoints behind a virtual-patch WAF rule (Patchstack and similar offer one) or restrict access to the CorvusPay IPN/callback URLs to CorvusPay's published source IP ranges at the web server or firewall - accepting the trade-off that IP changes by the processor could break legitimate payment confirmations. As an interim measure, manually reconcile order-paid status against the CorvusPay merchant dashboard rather than trusting plugin-reported payment state, and consider temporarily disabling the gateway if transaction volume is low enough to tolerate it.

Affected VersionsENISA

CorvusPay WooCommerce Payment Gateway n/a ≤2.7.4

Affected Packages

euvd corvuspay_woocommerce_payment_gateway no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the CorvusPay WooCommerce integration plugin, which bridges a WordPress/WooCommerce store to the CorvusPay payment processor, typically handling order checkout, redirect, and asynchronous payment-status callbacks. CWE-288 (Authentication Bypass Using an Alternate Path or Channel) indicates the plugin exposes a code path that reaches a protected action without performing the expected authentication or signature/verification check - a recurring pattern in payment-gateway plugins where the IPN/return endpoint trusts attacker-controllable input instead of cryptographically validating the processor's callback. Because the CVSS vector marks Integrity High with Confidentiality and Availability None, the practical effect is unauthorized state change (e.g., marking orders paid or altering integration logic) rather than data exposure, despite the source 'Information Disclosure' tag.

Know when Wordpress Plugin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (patchstack) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 7.5 HIGH

Unauthenticated network callback with no UI yields AV:N/AC:L/PR:N/UI:N; broken-auth state tampering gives I:H while C:N/A:N reflect no data exposure or downtime.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (patchstack).

CVSS VectorVendor: patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

DescriptionCVE.org

Unauthenticated Broken Authentication in CorvusPay WooCommerce Payment Gateway <= 2.7.4 versions.

Executive ViewAI

Why It Matters

CorvusPay WooCommerce Payment Gateway plugin (versions 2.7.4 and earlier) contains an unauthenticated authentication bypass allowing attackers to forge payment confirmations and manipulate transaction processing. Organizations using this plugin risk revenue leakage, fraud liability, and customer confidence loss with no vendor patch currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable the plugin immediately; (2) Implement cryptographic signature validation for payment callbacks; (3) Whitelist CorvusPay callback IP addresses; (4) Enable comprehensive transaction logging and real-time alerting for callback anomalies; (5) Conduct forensic review of all transactions processed since plugin installation.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Low
niche regional WooCommerce payment gateway plugin, limited install base
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy