Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify store using CorvusPay plugin
-
DeliverySend crafted request to callback endpoint
-
ExploitBypass authentication check (CWE-288)
-
ExecutionForge trusted payment/order state
-
ImpactUnauthorized 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
Primary rating from Vendor (patchstack).
CVSS VectorVendor: patchstack
DescriptionCVE.org
Unauthenticated Broken Authentication in CorvusPay WooCommerce Payment Gateway <= 2.7.4 versions.
Articles & Coverage 1
Executive ViewAI
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.
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-39692
GHSA-4jhm-9928-rqx4
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB