# DRUPAL-CONTRIB-2019-095: The Permissions by Term module extends Drupal by functionality for restricting access to single nodes via taxonomy terms.

> Attackers can view restricted node previews in search results when using the Search API module with Permissions by Term.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Dec 2019

## What is DRUPAL-CONTRIB-2019-095?

DRUPAL-CONTRIB-2019-095 is a missing authorization vulnerability in drupal/permissions_by_term, published on 11 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Permissions by Term module extends Drupal by functionality for restricting access to single nodes via taxonomy terms.

The module doesn't sufficiently restrict access to node previews, when the Search API module is used to display nodes in search result lists.

## Which versions are affected by DRUPAL-CONTRIB-2019-095?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/permissions_by_term` | Packagist:https://packages.drupal.org/8 | All versions | 2.0.0 |

## How do I fix DRUPAL-CONTRIB-2019-095?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2019-095 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2019-095 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2019-095 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2019-095 is a missing authorization vulnerability in drupal/permissions_by_term, published on 11 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2019-095 in the wild and no public exploit code.

Affected product: drupal/permissions_by_term. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2019-095/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2019-095/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2019-095

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2019-095/
Summaries are generated and may contain mistakes; the official description above is the record.