CVE-2025-31689 — gdpr
HIGHCVE-2025-31689 is a high-severity (CVSS 8.1) Cross-Site Request Forgery (CSRF) vulnerability in drupal/gdpr. A fix is available for drupal/gdpr — see the affected versions and patch details below.
General Data Protection Regulation - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2025-018
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-31689.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
drupal/gdpr🐘drupal/gdprReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Cross-Site Request Forgery (CSRF) vulnerability in Drupal General Data Protection Regulation allows Cross Site Request Forgery. This issue affects General Data Protection Regulation: from 0.0.0 before 3.0.1, from 3.1.0 before 3.1.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | drupal/gdpr | all versions | 3.0.1composer require drupal/gdpr:^3.0.1 |
| 🐘Packagist | drupal/gdpr | ≥ 3.1.0&&< 3.1.2 | 3.1.2composer require drupal/gdpr:^3.1.2 |
Affected Products
general data protection regulationgeneral_data_protection_regulation_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/gdpr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/gdpr to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-31689 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2025-31689 in your dependencies?
Find it across Packagist, including transitive dependencies.