# DRUPAL-CONTRIB-2018-067: The Workbench Moderation module adds arbitrary moderation states to Drupal core's "unpublished" and "published" node states, and affects the

> An access bypass in the Workbench Moderation module allows users to perform unauthorized content moderation transitions.

- **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:** 17 Oct 2018

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

DRUPAL-CONTRIB-2018-067 is an authentication bypass vulnerability in drupal/workbench_moderation, published on 17 Oct 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Workbench Moderation module adds arbitrary moderation states to Drupal core's "unpublished" and "published" node states, and affects the behavior of node revisions when nodes are published.

In some conditions, content moderation fails to check a users access to use certain transitions, leading to an access bypass.

This issue is related to the Drupal Core release [SA-CORE-2018-006](https://www.drupal.org/sa-core-2018-006).

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


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

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2018-067 is an authentication bypass vulnerability in drupal/workbench_moderation, published on 17 Oct 2018. 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-2018-067 in the wild and no public exploit code.

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

## Sources

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

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