Categories
CVE-2025-31684

Cross-Site Request Forgery (CSRF) in OAuth2 Client (CVE-2025-31684)

Summary

Vulnerability in OAuth2 Client (CVE-2025-31684). Data can be tampered with by attackers.

Original description

The description as published by the source.

Cross-Site Request Forgery (CSRF) vulnerability in Drupal OAuth2 Client allows Cross Site Request Forgery.This issue affects OAuth2 Client: from 0.0.0 before 4.1.3.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-2025-31684 has been found in OAuth2 Client.
Data can be tampered with by attackers.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OAuth2 Client CVE-2025-31684" on the vendor's site.

CVE-2025-31684 (OAuth2 Client) — CWE-352
Attack vector: remote (network-reachable) / unauthenticated
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 OAuth2 Client.

📍 Affected scope

Check the vendor advisory for the affected versions of OAuth2 Client.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで OAuth2 Client を使っているサービスとバージョンを洗い出す。

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

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

Affected packages

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

References

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