# DRUPAL-CONTRIB-2019-067: This module allows you to attach tabular data to an entity.

> Users with export permissions can access unpublished or restricted entity data due to insufficient access checks in the Tablefield 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:** 18 Sep 2019

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

DRUPAL-CONTRIB-2019-067 is a missing authorization vulnerability in drupal/tablefield, published on 18 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This module allows you to attach tabular data to an entity.

There is insufficient access checking for users with the ability to "Export Tablefield Data as CSV". They can export data from unpublished nodes or otherwise inaccessible entities.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "Export Tablefield Data as CSV".

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


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

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2019-067 is a missing authorization vulnerability in drupal/tablefield, published on 18 Sep 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-067 in the wild and no public exploit code.

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

## Sources

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

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