Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Drupal site with Commerce Realex module
-
DeliveryEnumerate or infer protected payment endpoint URLs
-
ExploitSend unauthenticated HTTP request to restricted path
-
ExecutionBypass authorization check via CWE-863 flaw
-
ImpactAccess order or transaction data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The target site must be running the Drupal Commerce Realex / Global Payments module in versions 0.0.0 through 3.0.2 (exclusive). The CVSS AC:H metric indicates that exploitation is not trivially automatable - the attacker likely needs to know or enumerate the specific protected URL paths exposed by the module, which may vary by site configuration. No authentication is required (PR:N), meaning the flaw is reachable by any network-accessible party. Exploitation is limited by the requirement to identify the exact vulnerable endpoints, the non-default knowledge of module-specific URL structures, and the restricted scope of impact (low confidentiality and integrity, no availability). Sites that deploy the module behind authentication-gated storefronts or with strict URL access controls at the web server level reduce but do not eliminate exposure. |
| Impact | Multiple signals converge on a moderate-to-low real-world priority. The CVSS 3.1 score is 4.8 (Medium) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N; the AC:H designation indicates exploitation is not straightforward and likely requires specific conditions such as knowledge of target URLs or a particular module configuration. EPSS is 0.18% at the 8th percentile, meaning fewer than 1 in 10 tracked CVEs have lower exploitation probability - a weak signal for opportunistic mass exploitation. SSVC confirms Exploitation: none, Automatable: no, Technical Impact: partial, which further de-prioritizes emergency response. The vulnerability is not listed in CISA KEV. The combination of PR:N (no credentials required) and network exposure is the primary concern, as it lowers the bar for any attacker who can identify the target endpoints. The impact is bounded - C:L and I:L with no availability impact - though in a payment context even limited data exposure or integrity modification carries business and compliance risk beyond raw CVSS. No conflicting signals between data sources; all sources consistently indicate limited exploitation pressure. |
| Exploit ScenarioDerived | An attacker targeting a Drupal e-commerce site identifies that it uses the Commerce Realex / Global Payments module, then enumerates or constructs the URL paths for protected payment confirmation or order-status endpoints. Without holding a user session or any credentials, the attacker directly browses to those paths, triggering the missing authorization check and gaining access to order details or potentially influencing transaction state. No public proof-of-concept code is known at time of analysis, and the AC:H rating suggests knowledge of specific endpoint paths or module configuration is a prerequisite. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 13, 2026
Incorrect Authorization (CWE-863) in the Drupal Commerce Realex / Global Payments module exposes protected payment and order resources to forceful browsing, allowing unauthenticated remote attackers to access endpoints that should require authorization. All module versions from 0.0.0 through 3.0.2 (exclusive) are affected on Drupal Commerce deployments. No public exploit code has been identified and SSVC confirms no active exploitation at time of analysis, though the nature of a payment gateway module means successful access could expose order or transaction data.
RemediationAI
Upgrade the Commerce Realex / Global Payments module to version 3.0.2 or later, as confirmed available by the vendor advisory at https://www.drupal.org/sa-contrib-2026-058. Drupal module updates can be applied via Composer (composer update drupal/commerce_realex) or through the Drupal administrative update interface. If immediate patching is not feasible, a compensating control is to restrict access to the payment module's callback and confirmation URL paths at the web server or reverse proxy layer using IP allowlisting for known payment gateway IP ranges from Realex / Global Payments - this limits the network exposure while degrading operational flexibility. An alternative is to temporarily disable the module and revert to manual order processing, though this has significant business impact. No generic workarounds are available that fully mitigate the authorization bypass without restricting module functionality.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in composer, 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 Drupal Commerce integration module for the Realex Payments / Global Payments gateway, identified by CPE cpe:2.3:a:drupal:commerce_realex_/_global_payments:*:*:*:*:*:*:*:*. CWE-863 (Incorrect Authorization) describes a failure to correctly verify that a requester is authorized to access a resource, distinct from authentication failures. The 'Forceful Browsing' descriptor indicates the module does not enforce authorization checks on one or more URL-addressable endpoints - an attacker who knows or guesses these paths can reach them directly without holding a valid session or role. In a payment gateway context, such endpoints may include order confirmation pages, payment return/callback handlers, or transaction status lookups, making improper access more impactful than in a generic content module.
Know when Commerce Realex Global Payments 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:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Network-accessible web module with no auth needed, but AC:H reflects required endpoint knowledge; C:L/I:L reflects bounded payment-data exposure with no availability impact.
Primary rating from Vendor (drupal).
CVSS VectorVendor: drupal
Lifecycle Timeline
5DescriptionCVE.org
Incorrect Authorization vulnerability in Drupal Commerce Realex / Global Payments allows Forceful Browsing. This issue affects Commerce Realex / Global Payments versions: from 0.0.0 to 3.0.2.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-43062
GHSA-2q62-xm7g-h9gh
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB