# DRUPAL-CONTRIB-2022-060: The Social Base theme is designed as a base theme for Open Social.

> Unauthenticated attackers can view titles of private groups via public content links, exposing sensitive group existence and names.

- **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:** 30 Nov 2022

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

DRUPAL-CONTRIB-2022-060 is a vulnerability in drupal/socialbase, published on 30 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Social Base theme is designed as a base theme for Open Social. This base  
theme holds has a lot of sensible defaults. It doesn't however contain much  
styling. We expect developers to want to change this for their own project.

When content within the Open Social distribution is placed within a group then the Socialbase theme renders a link to that group on the content view page.

The link to groups was rendered without sufficiently checking that the viewing user has access to the group. When creating public content in a non-public group this could lead to exposing the existence of the group and the group title to unauthorized users. The group itself remained inaccessible.

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/socialbase` | Packagist:https://packages.drupal.org/8 | From 2.3.0 | 2.3.4, 2.4.3 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: DRUPAL-CONTRIB-2022-060 is a vulnerability in drupal/socialbase, published on 30 Nov 2022. 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-2022-060 in the wild and no public exploit code.

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

## Sources

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

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