CVE-2025-13080

5.3 MEDIUM

📋 TL;DR

This vulnerability in Drupal core allows attackers to bypass access controls through forceful browsing, potentially accessing restricted content or functionality. It affects Drupal sites running vulnerable versions from 8.0.0 through 11.2.7.

💻 Affected Systems

Products:
  • Drupal core
Versions: 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
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All Drupal installations within affected version ranges are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could access sensitive administrative interfaces, user data, or privileged functionality they shouldn't have access to, potentially leading to data exposure or further system compromise.

🟠

Likely Case

Unauthorized access to restricted content areas, user profiles, or administrative pages that should require authentication or specific permissions.

🟢

If Mitigated

Limited impact with proper access controls, monitoring, and network segmentation in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Forceful browsing typically requires minimal technical skill and can be performed with standard web browsers or automated tools.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 10.4.9, 10.5.6, 11.1.9, 11.2.8

Vendor Advisory: https://www.drupal.org/sa-core-2025-005

Restart Required: No

Instructions:

1. Backup your Drupal site and database. 2. Update Drupal core to the patched version using Composer: composer update drupal/core-recommended --with-dependencies. 3. Run database updates: drush updatedb. 4. Clear caches: drush cache-rebuild.

🔧 Temporary Workarounds

Access Control Module Configuration

all

Tighten access control module settings to restrict access to sensitive paths

Web Application Firewall Rules

all

Implement WAF rules to block forceful browsing attempts to restricted paths

🧯 If You Can't Patch

  • Implement strict access control lists (ACLs) at the web server level to restrict access to sensitive paths
  • Deploy a web application firewall (WAF) with rules specifically targeting forceful browsing patterns

🔍 How to Verify

Check if Vulnerable:

Check Drupal version in admin/reports/status or via drush status

Check Version:

drush status | grep 'Drupal version' or check admin/reports/status page

Verify Fix Applied:

Verify Drupal version is 10.4.9+, 10.5.6+, 11.1.9+, or 11.2.8+

📡 Detection & Monitoring

Log Indicators:

  • Multiple 403 Forbidden errors for the same user/IP
  • Access attempts to restricted paths without proper authentication
  • Unusual access patterns to admin or privileged paths

Network Indicators:

  • HTTP requests to known restricted paths without authentication headers
  • Pattern of sequential path enumeration attempts

SIEM Query:

source="web_access_logs" (status=403 OR status=200) AND (uri CONTAINS "/admin/" OR uri CONTAINS "/user/") | stats count by src_ip, uri

🔗 References

📤 Share & Export