# DRUPAL-CONTRIB-2022-051: This module provides a widget to transform entity reference fields into a more user-friendly tags input component with a great performance.

> Authenticated users with edit permissions can view unpublished term data due to insufficient access checks in the tags input widget.

- **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:** 27 Jul 2022

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

DRUPAL-CONTRIB-2022-051 is a missing authorization vulnerability in drupal/tagify, published on 27 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This module provides a widget to transform entity reference fields into a more user-friendly tags input component with a great performance.

The module doesn't sufficiently check access for the add operation. Users with permission to edit content can view and reference unpublished terms. The edit form may expose term data that users could not otherwise see, since there is no term view route by default.

This vulnerability is slightly mitigated by the fact that an attacker must have a role with the permission "access content", so may not be accessible to anonymous users on all sites.

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


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

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2022-051 is a missing authorization vulnerability in drupal/tagify, published on 27 Jul 2022. 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-2022-051 in the wild and no public exploit code.

Affected product: drupal/tagify. 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-051/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2022-051/index.md)
```

## Sources

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

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