← Back
CVE-2026-13243
medium
CVSS 4.8
Cross-Site Request Forgery (CSRF) in drupal/salesforce (CVE-2026-13243)
Summary
vulnerability in drupal/salesforce (CVE-2026-13243). Risk of unauthorized operations or information disclosure. Exploitable via ``salesforce_oauth``. Mitigation: upgrade to `5.1.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-13243** has been found in drupal/salesforce.
Attackers can target a specific entry point like ``salesforce_oauth`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade drupal/salesforce to **5.1.3** or later.
If unsure, ask your IT team or search "drupal/salesforce CVE-2026-13243" on the vendor's site.
CVE-2026-13243 (drupal/salesforce) — CWE-352 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `salesforce_oauth` / `salesforce_jwt`
Patched: `5.1.3` — 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
**CSRF** (CWE-352) exists in drupal/salesforce. Attackers reach the vulnerable code path via ``salesforce_oauth`` without authentication.
📍 Affected scope
drupal/salesforce — . Attack surface: `salesforce_oauth` / `salesforce_jwt`.
🔥 Severity
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.1.3**.
🛡️ 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/salesforce' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'drupal/salesforce' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `drupal/salesforce` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade drupal/salesforce to 5.1.3ステージング環境で 5.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Packagist:https://packages.drupal.org/8
drupal/salesforce
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.3"}],"database_specific":{"constraint":"<5.1.3"}}]