Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-13233 low CVSS 3.3

SSRF (Server-Side Request Forgery) in drupal/ai_provider_openai (CVE-2026-13233)

Summary

SSRF in drupal/ai_provider_openai (CVE-2026-13233). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.1.1, 1.2.2 or later.

Original description

The description as published by the source.

This module enables you to use OpenAI as a provider for the AI module.

The module doesn't sufficiently sanitize user-supplied URLs, leading to a Server-side request forgery (SSRF) vulnerability.

This vulnerability is mitigated by the fact that an attacker must have the access to change the host url and a way to generate AI-generated images.

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-13233 has been found in drupal/ai_provider_openai.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade drupal/ai_provider_openai to 1.1.1, 1.2.2 or later.
If unsure, ask your IT team or search "drupal/ai_provider_openai CVE-2026-13233" on the vendor's site.

CVE-2026-13233 (drupal/ai_provider_openai) — CWE-918 / CVSS v3 3.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.1.1, 1.2.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

SSRF (CWE-918) exists in drupal/ai_provider_openai.

📍 Affected scope

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

🔥 Severity

Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.1.1, 1.2.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/ai_provider_openai' . 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/ai_provider_openai' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade drupal/ai_provider_openai to 1.1.1, 1.2.2

    ステージング環境で 1.1.1, 1.2.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/ai_provider_openai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.1"}],"database_specific":{"constraint":"<1.1.1"}},{"type":"ECOSYSTEM","events":[{"introduced":"1.2.0"},{"fixed":"1.2.2"}],"database_specific":{"constraint":">=1.2.0 <1.2.2"}}]

References

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