# DRUPAL-CONTRIB-2022-016: **Update** Maintainers stepped forward, fixed the security issue, and Vocabulary Permissions Per Role is supported again.

> An unauthorized user can view, modify, and delete vocabulary terms due to missing access checks in the Vocabulary Permissions Per Role module.

- **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:** 25 Jan 2022

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

DRUPAL-CONTRIB-2022-016 is a missing authorization vulnerability in drupal/vppr, published on 25 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

**Update**  
Maintainers stepped forward, fixed the security issue, and Vocabulary Permissions Per Role is supported again.

The module allows adding to/editing terms of/removing terms from vocabularies per role.

The module did not properly check access for certain operations allowing an unauthorized malicious user to view, modify and delete terms.

**Original advisory**  
The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: <https://www.drupal.org/node/251466#procedure---own-project---unsupported>

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


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

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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