dbcve.org
General Data Protection RegulationApplication · General Data Protection Regulation Project

CVE-2025-31689

HIGH · 8.1 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 3.0.1 / 3.1.2 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Drupal General Data Protection Regulation module allows attackers to trick authenticated users into performing unintended administrative actions. The vulnerability affects versions 3.0.0 and 3.1.0-3.1.1.

MitigationUpdate the Drupal General Data Protection Regulation module to version 3.0.1 or 3.1.2 or later to obtain the CSRF token validation fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
General Data Protection RegulationApplication
Affected:< 3.0.1>= 3.1.0, < 3.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the GDPR module installation directory
    Check the Drupal modules directory for the 'gdpr' folder. Common paths include /modules/gdpr, /sites/all/modules/gdpr, or /web/modules/gdpr depending on your installation structure.
    Affected if The module folder does not exist, meaning GDPR module is not installed.
  2. Determine the installed GDPR module version
    Open the gdpr.info.yml or gdpr.module file within the gdpr module directory and read the 'version' or 'core' and package information. Alternatively, run 'drush pm-list --type=module --filter=gdpr' if Drush is available, or query the Drupal database system table for the gdpr module entry.
    Affected if Unable to retrieve version information indicates the module may not be installed.
  3. Compare installed version against affected ranges
    Compare the version found in step 2 to the affected ranges: versions 3.0.0 and 3.1.0 through 3.1.1. The environment is vulnerable if the version is 3.0.0 or between 3.1.0 and 3.1.1 inclusive.
    Affected if The installed version falls within 3.0.0 or 3.1.0-3.1.1.
  4. Verify the module is enabled for the vulnerability to apply
    Confirm the GDPR module status is 'Enabled' in Drupal admin at /admin/modules, via Drush with 'drush pm-list --status=enabled --type=module | grep gdpr', or by checking the 'status' field in the system database table for the gdpr module.
    Affected if The module is installed but disabled; the CSRF vulnerability cannot be exploited if the module is not active.

The environment is affected if the GDPR module is enabled and the installed version is 3.0.0 or between 3.1.0 and 3.1.1.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.0.1 / 3.1.2 or later
Fixed in 3.0.13.1.2
Interim mitigation

Update the Drupal General Data Protection Regulation module to version 3.0.1 or 3.1.2 or later to obtain the CSRF token validation fix.

Recommended fix High confidence

Upgrade to GDPR module 3.0.1 or 3.1.2 (or later)

  1. 1. Back up your Drupal site database and files.
  2. 2. If using Composer for Drupal module management, run: composer require drupal/gdpr:^3.0.1 or composer require drupal/gdpr:^3.1.2
  3. 3. Alternatively, download the GDPR module version 3.0.1 or 3.1.2 from www.drupal.org/project/gdpr
  4. 4. Install the updated module following standard Drupal module update procedures.
  5. 5. Clear Drupal caches: drush cr all or through admin menu at /admin/config/development/performance
  6. 6. Verify the update was successful by checking the module version at /admin/modules
Caveat Review GDPR module release notes for any configuration or feature changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in General Data Protection Regulation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31689 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31689 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data