DrupalCMS
CVE-2025-13080
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 · uneditedImproper Check for Unusual or Exceptional Conditions vulnerability in Drupal Drupal core allows Forceful Browsing.This issue affects Drupal core: from 8.0.0 before 10.4.9, from 10.5.0 before 10.5.6, from 11.0.0 before 11.1.9, from 11.2.0 before 11.2.8.
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 · high confidenceThis is an Improper Check for Unusual or Exceptional Conditions vulnerability in Drupal core that allows Forceful Browsing - enabling unauthorized access to protected pages or resources that should require authentication or specific permissions. The vulnerability exists in Drupal core versions 8.0.0 through 10.4.8, 10.5.0-10.5.5, 11.0.0-11.1.8, and 11.2.0-11.2.7.
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
DrupalCMS
>= 8.0.0, < 10.4.9>= 10.5.0, < 10.5.6>= 11.0.0, < 11.1.9>= 11.2.0, < 11.2.8CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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.
-
Check Drupal core version via DrushRun `drush status | grep "Drupal version"` or `drush core:status` to retrieve the installed Drupal core versionAffected if Version falls within 8.0.0-10.4.8, 10.5.0-10.5.5, 11.0.0-11.1.8, or 11.2.0-11.2.7
-
Check Drupal core version via composer or fileRun `composer show drupal/core 2>/dev/null | grep "versions"` or inspect the CHANGELOG.txt file in the Drupal root directory for the version numberAffected if Version falls within the affected ranges listed above
-
Verify protected routes existInspect the Drupal routing configuration by examining the routing.yml files in your modules or themes, or use `drush route-list` to see registered routesAffected if Routes requiring authentication (login, admin, or other protected paths) are defined in the system
-
Check for unauthorized access to protected pagesTest accessing protected routes directly via URL without authenticating, or review access logs for requests to protected paths that bypassed loginAffected if Protected pages or resources are accessible without proper authentication or permissions
You are affected if your Drupal core version is within the affected ranges AND your site has protected routes or resources that could be accessed without proper authorization.
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 · scoped10.4.910.5.611.1.9
Upgrade Drupal core to version 10.4.9, 10.5.6, 11.1.9, or 11.2.8 (whichever falls within your release line) to patch this access control vulnerability.
Upgrade to the latest stable release in your current major version line: 10.4.9+, 10.5.6+, 11.1.9+, or 11.2.8+
- 1. Identify the current Drupal core version by checking the CHANGELOG.txt file or running `drush status`
- 2. Determine the appropriate upgrade path based on current version:
- - If on 10.3.x or 10.4.x: upgrade to 10.4.9 or later
- - If on 10.5.x: upgrade to 10.5.6 or later
- - If on 11.0.x or 11.1.x: upgrade to 11.1.9 or later
- - If on 11.2.x: upgrade to 11.2.8 or later
- 3. Before upgrading, back up the entire database and codebase
- 4. Review the upgrade path documentation at https://www.drupal.org/docs/upgrading-drupal
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Drupal
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13080 — 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-13080 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