# DRUPAL-CONTRIB-2020-033: The Group module enables you to hand out permissions on a smaller subset, section or community of your website.

> Non-members can gain elevated permissions on grouped content if two group types with conflicting permissions are configured for the same content type.

- **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:** 5 Aug 2020

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

DRUPAL-CONTRIB-2020-033 is a missing authorization vulnerability in drupal/group, published on 5 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Group module enables you to hand out permissions on a smaller subset, section or community of your website.

Under very specific circumstances, where two group types support the same content, yet hand out different permissions, non-members of the first group type may use the set of permissions of the 2nd group type for the grouped content.

This vulnerability is mitigated by the fact that you must already have a rare set-up and the two group types are configured in a way where one is more permissive than the other over the same type of content.

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


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

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2020-033 is a missing authorization vulnerability in drupal/group, published on 5 Aug 2020. 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-2020-033 in the wild and no public exploit code.

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

## Sources

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

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