# DRUPAL-CONTRIB-2020-016: This webform module enables you to build 'Term select' and 'Term checkboxes' elements.

> The Drupal webform module exposes unpublished taxonomy terms to unauthorized users, allowing information disclosure.

- **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:** 6 May 2020

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

DRUPAL-CONTRIB-2020-016 is a vulnerability in drupal/webform, published on 6 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This webform module enables you to build 'Term select' and 'Term checkboxes' elements.

The module doesn't sufficiently check term 'view' access when rendering the 'Term select' and 'Term checkboxes' elements. Unpublished terms will always appear in the 'Term select' and 'Term checkboxes' elements.

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


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

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2020-016 is a vulnerability in drupal/webform, published on 6 May 2020. 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-2020-016 in the wild and no public exploit code.

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

## Sources

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

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