# DRUPAL-CONTRIB-2022-055: This module enables you to restrict content via taxonomy terms and related permissions.

> An attacker can view restricted cached content if multiple entity types are enabled in the Drupal taxonomy restriction module.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Sep 2022

## What is DRUPAL-CONTRIB-2022-055?

DRUPAL-CONTRIB-2022-055 is a missing authorization vulnerability in drupal/permissions_by_term, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This module enables you to restrict content via taxonomy terms and related permissions.

The module doesn't sufficiently restrict cached content in certain circumstances.

This vulnerability is mitigated by the fact that it only occurs when multiple entity types are enabled in the module.

## Which versions are affected by DRUPAL-CONTRIB-2022-055?


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

## How do I fix DRUPAL-CONTRIB-2022-055?

Apply the vendor's patch.

## Is DRUPAL-CONTRIB-2022-055 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2022-055 is a missing authorization vulnerability in drupal/permissions_by_term, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2022-055 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-2022-055/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2022-055/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2022-055

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