Skip to main content

Commerce Realex / Global Payments CVE-2026-13238

| EUVDEUVD-2026-43062 MEDIUM
Incorrect Authorization (CWE-863)
2026-07-10 drupal GHSA-2q62-xm7g-h9gh
4.8
CVSS 3.1 · Vendor: drupal
View

Attack ChainAIDerived

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

  1. Access
    Identify Drupal site with Commerce Realex module
  2. Delivery
    Enumerate or infer protected payment endpoint URLs
  3. Exploit
    Send unauthenticated HTTP request to restricted path
  4. Execution
    Bypass authorization check via CWE-863 flaw
  5. Impact
    Access 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – 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

Commerce Realex / Global Payments 0.0.0 <3.0.2

Affected Packages

composer drupal/commerce_realex fix: 3.0.2
euvd commerce_realex_global_payments fix: 3.0.2

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

Vendor (drupal) PRIMARY 4.8 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
vuln.today AI 4.8 MEDIUM

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.

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

Primary rating from Vendor (drupal).

CVSS VectorVendor: drupal

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

Lifecycle Timeline

5
Severity Changed
Jul 13, 2026 - 19:22 NVD
CRITICAL MEDIUM
CVSS changed
Jul 13, 2026 - 19:22 NVD
9.1 (CRITICAL) 4.8 (MEDIUM)
CVSS changed
Jul 13, 2026 - 19:07 NVD
9.1 (CRITICAL)
Patch available
Jul 10, 2026 - 23:02 EUVD
CVE Published
Jul 10, 2026 - 21:44 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.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

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Low
niche Drupal payment gateway module, limited to specific e-commerce deployments
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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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