Restrict Route By IpDrupal extension · Restrict Route By Ip Project
CVE-2025-47701
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Drupal Restrict route by IP allows Cross Site Request Forgery.This issue affects Restrict route by IP: from 0.0.0 before 1.3.0.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Drupal 'Restrict route by IP' module allows attackers to trick authenticated users into unknowingly performing actions they did not intend, potentially modifying IP-based route restrictions without consent.
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
Restrict Route By IpDrupal extension
>= 1.0.0, < 1.3.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the module is installedRun 'drush pm:list --type=module' or check for the restrict_route_by_ip directory in modules/contrib/Affected if The module 'Restrict route by IP' appears in the module list
-
Determine the installed module versionCheck the version field in the module's .info.yml file located at modules/contrib/restrict_route_by_ip/restrict_route_by_ip.info.yml, or run 'drush pm:info restrict_route_by_ip'Affected if The reported version is 1.0.0, 1.1.0, 1.2.0, or any version less than 1.3.0
-
Confirm the module is enabledVerify the module status in Drupal admin at /admin/modules, or check the 'status' field in the Drush pm:info outputAffected if The module shows as 'Enabled' or 'Installed'
-
Check if IP route restrictions are configuredInspect Drupal configuration for restrict_route_by_ip settings, typically found via Drush with 'drush cex' or in the config table for items containing 'restrict_route_by_ip', or access the module configuration page at /admin/config/system/restrict-route-by-ipAffected if Any IP-based route restrictions have been defined in the module settings
You are affected if the Restrict route by IP module is enabled at version 1.0.0 through 1.2.x and has IP route restrictions configured, as this combination allows the CSRF attack vector to target your authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.0
Update the Restrict route by IP module to version 1.3.0 or later, which should include proper CSRF token validation for state-changing operations.
1.3.0
- Backup your Drupal site database and files
- Update the Restrict route by IP module using Composer: composer require drupal/restrict_route_by_ip:^1.3.0 or use the Drupal admin UI to check for updates and install version 1.3.0
- Run database updates if prompted: drush updatedb or via the admin UI at /update.php
- Clear Drupal caches: drush cr or via the admin UI at /admin/config/development/performance
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Restrict Route By Ip
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47701 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47701 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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