Is drupal/permissions_by_term vulnerable?

Composer drupal/permissions_by_term has 6 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

6advisories

0critical

0on CISA KEV

0no fix recorded

CVE	Title	Severity	Affected	Fixed in
CVE-2026-107311	This module enables you to restrict view access to single nodes via taxonomy terms. The module doesn't sufficiently che	unknown	`<3.1.41`	`3.1.41`
DRUPAL-CONTRIB-2017-082	The Permissions by Term module extends Drupal by adding functionality for restricting access to single nodes via taxonom	unknown	`<1.35.0`	`1.35.0`
DRUPAL-CONTRIB-2019-068	This module enables you to control access to content based on taxonomy terms. The module doesn't sufficiently check if a	unknown	`<2.11.0`	`2.11.0`
DRUPAL-CONTRIB-2019-095	The Permissions by Term module extends Drupal by functionality for restricting access to single nodes via taxonomy terms	unknown	`<2.0.0`	`2.0.0`
DRUPAL-CONTRIB-2022-055	This module enables you to restrict content via taxonomy terms and related permissions. The module doesn't sufficiently	unknown	`<3.1.19`	`3.1.19`
DRUPAL-CONTRIB-2022-056	This module enables you to set content permissions based on taxonomy terms. The module doesn't sufficiently restrict ac	unknown	`<3.1.19`	`3.1.19`

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs How findings are ranked

A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.