This module enables you to share users, content and configuration across a group of domains from a single Drupal installation.
Description
A vulnerability exists in the Drupal Domain Access module versions prior to 3.0.2 where insufficient checks are performed on domain assignments when the per-content-type grant setting is enabled. This setting is off by default. Exploitation requires the attacker to have specific permissions and be assigned to at least one domain.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Drupal Domain Access module allows sharing of users, content, and configuration across multiple domains from a single installation. Its Domain Access submodule controls domain-specific content editing permissions. When the optional per-content-type grant setting is enabled, the module does not sufficiently verify which domains a user is assigned to, potentially allowing unauthorized content edits or deletions. Successful exploitation requires that the attacker holds a role with the permission "Edit any content on assigned domains" or "Delete any content on assigned domains" along with a per-content-type permission such as "Article: Edit any content on assigned domains", and that the attacker is assigned to at least one domain. The vulnerability is fixed in version 3.0.2.
Potential Impact
An attacker with the necessary permissions and domain assignments could potentially edit or delete content on domains they should not have access to, violating content access controls. However, exploitation is limited by the requirement that the per-content-type grant setting be enabled (off by default) and the attacker must already have elevated permissions and domain assignments.
Mitigation Recommendations
Upgrade the Drupal Domain Access module to version 3.0.2 or later where this vulnerability is fixed. If upgrading is not immediately possible, ensure the per-content-type grant setting remains disabled (default off) to mitigate the risk. Review user roles and permissions to limit assignment of the relevant content editing and deletion permissions to trusted users only.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- DRUPAL-CONTRIB-2026-238
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Packagist:https://packages.drupal.org/8"]
Threat ID: 6ad91ca84d27ba8daafa91b6
Added to database: 10/21/2026, 20:12:24 UTC
Last enriched: 10/21/2026, 20:14:02 UTC
Last updated: 10/21/2026, 20:14:02 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.