Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-13238 medium CVSS 4.8

Authorization Flaw in drupal/commerce_realex (CVE-2026-13238)

Summary

Vulnerability in drupal/commerce_realex (CVE-2026-13238). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.0.2 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-13238 has been found in drupal/commerce_realex.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade drupal/commerce_realex to 3.0.2 or later.
If unsure, ask your IT team or search "drupal/commerce_realex CVE-2026-13238" on the vendor's site.

CVE-2026-13238 (drupal/commerce_realex) — CWE-863 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.0.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Incorrect authorization (CWE-863) exists in drupal/commerce_realex.

📍 Affected scope

Check the vendor advisory for the affected versions of drupal/commerce_realex.

🔥 Severity

Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'drupal/commerce_realex' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'drupal/commerce_realex' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で drupal/commerce_realex を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade drupal/commerce_realex to 3.0.2

    ステージング環境で 3.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist:https://packages.drupal.org/8 drupal/commerce_realex
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.2"}],"database_specific":{"constraint":"<3.0.2"}}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details