Domain
The module does not sufficiently check which domains a user is assigned to when the per content type grant setting is enabled. An ordinary account on the site could view restricted domain information and alter or add new content across domains.
- Who could do thisOnly someone with a login on your site.
- Does it apply to youThe per content type grants setting must be enabled, and an attacker must have a role with the access right to edit or delete any content on assigned domains together with a per content type access right, and must be assigned to at least one domain.
- Has it been used in attacksNo sign of it.
- How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.
Tell your developerUpdate Domain to 3.0.2.
For developers: what the fix changed
Fixes an access bypass in `DomainAccessNodeHooks` by ensuring that users must be assigned to at least one domain before evaluating per-bundle update or delete grants.
Also in this release The release also includes numerous bug fixes, PHPStan and CSpell corrections, test updates for Drupal 11.4, and documentation additions.
.cspell-project-words.txt+3 −0README.md+1 −1docs/domain_config/index.es.md+6 −1docs/domain_config/index.fr.md+6 −1docs/domain_config/index.md+6 −1docs/index.es.md+1 −1docs/index.fr.md+1 −1docs/index.md+1 −1docs/metrics.md+248 −0domain/config/install/field.field.user.user.field_domain_admin.yml+6 −4domain/config/schema/domain.schema.yml+7 −0domain/domain.install+12 −1